[Bug 55994] New: module:import_dll Library WDFLDR.SYS (which is needed by L"C:\\windows\\system32\\drivers\\DBUtilDrv2.sys") not found
https://bugs.winehq.org/show_bug.cgi?id=55994
Bug ID: 55994 Summary: module:import_dll Library WDFLDR.SYS (which is needed by L"C:\windows\system32\drivers\DBUtilDrv2.sys") not found Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mikes@kuentos.guam.net Distribution: ---
Upgraded to the new 9.0-rc1 on machine Run wine notepad with regular user and it works fine. Running with root user get this. 00e0:err:module:import_dll Library WDFLDR.SYS (which is needed by L"C:\windows\system32\drivers\DBUtilDrv2.sys") not found 00e0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\DBUtilDrv2": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"DBUtilDrv2" failed to start: 1114
notepad does open not sure why this message appears with root user?
https://bugs.winehq.org/show_bug.cgi?id=55994
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- (In reply to Michael Setzer II from comment #0)
notepad does open not sure why this message appears with root user?
The default prefix location is $HOME/.wine, so simply running wine as root will change that. (See [1] for an explanation of what a prefix is.) My guess is that some point you installed a Windows kernel driver for something while running Wine as root.
Unless you need the driver for something, I would recommend just deleting the prefix and ignoring this bug. Also, don't run Wine as root; see [2].
[1] https://wiki.winehq.org/FAQ#Wineprefixes
[2] https://wiki.winehq.org/FAQ#Should_I_run_Wine_as_root.3F
https://bugs.winehq.org/show_bug.cgi?id=55994
--- Comment #2 from Michael Setzer II mikes@kuentos.guam.net --- Thanks for the quick reply.
Had just installed a new Fedora 39 on a notebook, so was just a clean install. Don't use the wine under root on other systems (Fedora 38) for anything other than quick testing of various options. I'll have to check what the prefix is set for, since I did nothing other than run wine notepad with the root.
There is no such error message on the Fedora 38 machines, so perhaps it is the default prefix??
Generally, do a wine notepad on both regular user and the root user after a winehq update to have it make changes to setups. Just noticed the errors on the Fedora 39.
Thanks for info.
https://bugs.winehq.org/show_bug.cgi?id=55994
--- Comment #3 from Zeb Figura z.figura12@gmail.com --- DBUtilDrv2.sys is not shipped with Wine. I don't know what kind of driver it's supposed to be, but it must have been installed intentionally, perhaps packaged with some other Windows software.
https://bugs.winehq.org/show_bug.cgi?id=55994
--- Comment #4 from Michael Setzer II mikes@kuentos.guam.net --- That is strange thing. I have not installed anything in either the regular user or the root user after installing the winehq devel version.
with regular user run wine notepad and it does update to wine, and loads notepad with no error messages
doing wine notepad with root user shows that message.
So don't know why the root version is looking for the non-existing files..
Again, on my machines with Fedora 38 the root user does not show that error messages..
Thanks again.
https://bugs.winehq.org/show_bug.cgi?id=55994
--- Comment #5 from Michael Setzer II mikes@kuentos.guam.net --- Looked for those files from errors and couldn't find them. Then did this from /root/.wine/drive_c find . | grep DBU ./windows/inf/DBUtilDrv2.pnf ./windows/inf/DBUtilDrv2.inf ./windows/system32/drivers/DBUtilDrv2.sys ./windows/system32/catroot/{f750e6c3-38ee-11d1-85e5-00c04fc295ee}/DBUtilDrv2.cat
Now discovered what it was. Seems Dell has a Bios update utility that I had downloaded. Was expecting it to extract a bios file that could be updated from bios. Ran it, and guess it installed those thing.
Web page said it would work with Unbuntu linux but didn't do anything with the Fedora. Later found that the notebook had the latest bios installed, so need to look further.
Delete the /root/.wine directory completely since hadn't done anything. Than ran wine notepad and it recreated and no error.
Thanks again for your time.
https://bugs.winehq.org/show_bug.cgi?id=55994
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Zeb Figura z.figura12@gmail.com --- That'd do it.
It's very unlikely that Wine is capable of running a BIOS update utility, since it'd need to be able to access the hardware at a kernel level. So I'm going to tentatively resolve this as WONTFIX.
https://bugs.winehq.org/show_bug.cgi?id=55994
--- Comment #7 from Michael Setzer II mikes@kuentos.guam.net --- That is fine, since it wasn't actually a problem with wine.
I had run the program from dell site with the bios program that said it was for the Unbunta version, but was an exe file. I thought it was going to be a self extracting file that contained the bios file, that could then be copied to an usb disk and installed with boot bios option. But running it gave an error message, and produced no output file. Didn't see anything that it had installed those files.
Thanks for your time.
https://bugs.winehq.org/show_bug.cgi?id=55994
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Austin English austinenglish@gmail.com --- Closing.
-
WineHQ Bugzilla