[Bug 41713] Initial 'explorer' process fails to register/run ShellWindows class local COM server in new WINEPREFIX due to incomplete registry data

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=41713

--- Comment #8 from Anastasius Focht <focht at gmx.net> ---
Hello again,

adding another way to reproduce the problem without even having tests compiled.

Taken from my analysis https://bugs.winehq.org/show_bug.cgi?id=45600#c3

--- snip ---
# run against existing WINEPREFIX
# 9ba05972-f6a8-11cf-a442-00a0c90a8f39 -> CLSID_ShellWindows

$ while true ; do wine cmd.exe /c "echo test >
\\\\.\\pipe\\{9ba05972-f6a8-11cf-a442-00a0c90a8f39}" ; sleep 1 ; done

0034:fixme:ntdll:server_get_file_info Unsupported info class 14
Invalid function.

0036:fixme:ntdll:server_get_file_info Unsupported info class 14
Invalid function.

...
# kill explorer process/local COM server
...
File not found.
--- snip ---

'Invalid function.' -> ok, named pipe can be opened
'File not found.' -> error, named pipe does not exist (COM server not running)

If this is run against a newly created WINEPREFIX it will always fail. Just use
some builtin app to bootstrap and keep it from being shut down.

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.