https://bugs.winehq.org/show_bug.cgi?id=36142
--- Comment #5 from Anastasius Focht focht@gmx.net --- Hello folks,
I think there was a misunderstanding here.
My original comment:
--- quote --- Adding the minimal set of keys manually lets the installer continue (only to run into next bug).
<registry snippet>
<log output> ... 2014-04-28-12-31-56-831 : 0x0034 : Information : OpenService(RpcSs, 0x1) 2014-04-28-12-31-56-832 : 0x0034 : Information : OpenService(RpcSs, 0x3) 2014-04-28-12-31-56-832 : 0x0034 : Information : ChangeServiceConfig(RpcSs, 2, C:\windows\system32\svchost.exe -k rpcss, (null), Remote Procedure Call (RPC))
--- quote ---
doesn't talk about adding a single registry key to trick the installer.
With "service entry" I meant having a *valid* entry for the service control manager to be able to manage/recognize it as service (like builtin 'Lanman Server', 'Task Scheduler', 'WIA Service' ...) - even if it would be fake.
The installer doesn't simply check the registry entry but tries to open the service via SCM. That single registry key added by the commit won't do any good - it's simply ignored by SCM on startup:
--- snip --- ... trace:service:scmdatabase_load_services Loading service L"RpcSs" trace:service:load_service_config Image path = (null) trace:service:load_service_config Group = (null) trace:service:load_service_config Service account name = (null) trace:service:load_service_config Display name = (null) trace:service:load_service_config Service dependencies : (none) trace:service:load_service_config Group dependencies : (none) trace:service:scmdatabase_load_services Even the service type not set for service L"RpcSs" - skipping ... --- snip ---
Regards