Leaderboard

... will have received, by then (when actually EoS), ... Do rest assured you do wield a pretty good and nuanced English.

can't be done as the feature has been removed. scaling can be added back to control panel via an old display.dll but resolution page is gone.

Apparently all versions including the current 14 are supported under XP: https://community.teamviewer.com/t5/Knowledge-Base/Which-operating-systems-are-supported/ta-p/24141#toc-hId--1332302068 As for me, I'm still using version 12, which I've been very happy with (12.1.12295): http://sdfox7.com/xp/sp3/EOL/TeamViewer_Setup.exe Later releases of version 12 had stability issues so I chose not to update. You can download earlier versions of TeamViewer 13 to 10 here (Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP): https://www.teamviewer.com/en/download/previous-versions/ You can download legacy versions of TeamViewer 5 to 9 here (Windows 98, Windows NT 4.0, Windows 2000): https://www.teamviewer.com/en/download/old-versions.aspx

The exception information can be logged in event log, but it probably contains only value 0x8000FFFF, because the code just calls ModuleFailFastForHRESULT(0x8000FFFF) in this situation. As to debugging, if I use virtual machine, I can connect remote debugger to it and debug the assembly normally as any other application. But for local debugging, I can use only printf logs (or dump file for crashes), because attaching the debugger to DWM stops the desktop rendering .

@Mcinwwl Have tested the versions 13.2.26558.0 and 14.1.3399.0, both worked for me. I do not use IP6.

I reinstalled 7.38 a few weeks ago, and today the update nag came back. Back on 7.36 now.

Compatibility engine is present regardless. And so is the default compatibility database. Judging from the strings in apphelp.dll, there's a flag in compatibility database that says it shouldn't be loaded on that version of the OS. Consequently, you may have a buggy Win9x era application that works out-of-the-box on full XP, but crashes and burns on FLP. Nevertheless, it's still possible to apply compatibility fixes with Compatibility Administrator v5.0 that comes with Microsoft Application Compatibility Toolkit v5.5. It's also possible to install newer, also easier to find 5.6 version of the toolkit, but its Compatibility Administrator can't read application entries from system database on XP, which might be useful for reference.

Well here is some info about creating items in Control Panel https://msdn.microsoft.com/en-us/library/windows/desktop/hh127450(v=vs.85).aspx And the CLSID list for some objects in Windows 10: https://www.tenforums.com/tutorials/3123-clsid-key-guid-shortcuts-list-windows-10-a.html On Windows 7 Pro, running explorer shell:::{C555438B-3C23-4769-A71F-B6D3D9B6053A} will launch the Display panel, but on Windows 10 Enterprise 1803 it gives an error. So perhaps in 1803 it is different than on that site and you would have to dig abour in the registry to find the correct CLSID.

@roytam1 Thanks a lot, everything is back to normal again . Also thanks to @VistaLover , his detailed post saved us (again).

just have a deeper look into PM's webRTC code, its module is not updated to fx52 level and javascript module fails when loading https://test.webrtc.org/ demo. so I decided to disable it again. EDIT: pm28 builds updated

Thanks @fernman, that's what this forum (and others like it of course) is all about!

Thank you from the bottom of my heart , i had the same error message and suddenly all the applications of microsoft office 2010 didn't work anymore. Luckily there are people like you that share their experiences! I removed the updates that you indicate and now it's all ok. Have a good day, thanks again.

...but nowhere in the world masses of people actually cried for this. ...as a matter f fact the very few people that got one legally were extremely happy for having NOT "Rover" in the search dialog. AFAIK a number of "missing features" listed are actually "good, intelligent removal of senseless bloat" . jaclaz