The old style Computer Management\Windows Logs\System Logs shows loads of DCOM errors aka W5,6,7,8,8.1. Why do we still get these errors and when will MSFT release a simple to user tool to fix 'em.
The current palava of having to open up the Registry, CLSID & APPID listings, locate the gobbledegook clisid/appid entry, reset the security permissions entries for Owner etc. then go to Control Panel, Admin Tools, Component Services, Computer, My Computer DCOM, locate the relevant error such as Runtime Broker ( a very common one) and then fix the permissions - again - is just such a time wasting bore and so very prone to making mistakes or breaking some other service/function.
Come on MSFT, get your computing heads together and fix these decades old problems with all versions of Windows before trying to flog us yet more graphical UI 'updates' to this very very old NT OS.
The current palava of having to open up the Registry, CLSID & APPID listings, locate the gobbledegook clisid/appid entry, reset the security permissions entries for Owner etc. then go to Control Panel, Admin Tools, Component Services, Computer, My Computer DCOM, locate the relevant error such as Runtime Broker ( a very common one) and then fix the permissions - again - is just such a time wasting bore and so very prone to making mistakes or breaking some other service/function.
Come on MSFT, get your computing heads together and fix these decades old problems with all versions of Windows before trying to flog us yet more graphical UI 'updates' to this very very old NT OS.
Facebook
Twitter
Instagram