Command line rules.
The service guides used for reference do not mention DCOM so it was test disabled.
https://www.blackviper.com/service-configurations/black-vipers-windows-xp-x86-32-bit-service-configurations/
https://www.overclockersclub.com/guides/windows_xp_services/2.htm
Disabling DCOM Server Process Launcher via 'services.msc' causes the GUI to become non-functional ( without warning! ), not allowing the service to be re-started.
Upon reboot the system has poor function (safe mode too) but it's still possible to Ctrl-Alt-Delete to access Task Manager and get a runbox to launch 'cmd'. Alternatively press F8 at boot and select 'Safe Mode with Command Prompt'.
Reconfigure DCOM via command line, note space after 'start=':
sc config dcomlaunch start= auto
Very helpful including services reference:
https://www.windows-commandline.com/start-stop-service-command-line/
The service guides used for reference do not mention DCOM so it was test disabled.
https://www.blackviper.com/service-configurations/black-vipers-windows-xp-x86-32-bit-service-configurations/
https://www.overclockersclub.com/guides/windows_xp_services/2.htm
Disabling DCOM Server Process Launcher via 'services.msc' causes the GUI to become non-functional ( without warning! ), not allowing the service to be re-started.
Upon reboot the system has poor function (safe mode too) but it's still possible to Ctrl-Alt-Delete to access Task Manager and get a runbox to launch 'cmd'. Alternatively press F8 at boot and select 'Safe Mode with Command Prompt'.
Reconfigure DCOM via command line, note space after 'start=':
sc config dcomlaunch start= auto
Very helpful including services reference:
https://www.windows-commandline.com/start-stop-service-command-line/