4.3.28 installation failed

[Josk]

Hi, I tried to install 4.3.28 but I had a bluescreen during installation saying DPC_WATCHDOG_VIOLATION. I tried after to install the 4.3.26 again and it failed. I tried to do all sorts of fix found on your forums but nothing worked. I link to this bug report a log of the last installation I tried

[Josk]

Installation log

[Petr Vones]

Important information from MSI log is:

DIFXAPP: INFO:   Could not open file C:\Windows\System32\DriverStore\FileRepository\vboxusb.inf_amd64_d9689a9f7361dd1a\vboxusb.inf. (Error code 0x3: Le chemin d’accès spécifié est introuvable.)

DIFXAPP: ERROR: encountered while installing driver package 'D:\Program Files\Oracle\VirtualBox\drivers\USB\device\VBoxUSB.inf'

[Frank Mehnert]

Did you already try to uninstall VirtualBox, reboot the host and install VirtualBox 4.3.28?

[Josk]

Replying to frank:

Did you already try to uninstall VirtualBox, reboot the host and install VirtualBox 4.3.28?

Yup, but the fact is that after the bluescreen, I tried to install 4.3.26. It failed, so I went to the Programs category of my computer and VirtualBox wasn't there anymore(so it was uninstalled for the system, but the files were here). So I can't uninstall anymore, and install fail everytime leaving files on my disk

[Petr Vones]

Have you tried to uncheck USB support in installer options ?

[Josk]

Replying to Petr Vones:

Have you tried to uncheck USB support in installer options ?

Will it cause problems with the emulation after? (And it doesn't explain the bluescreen every time I try to install 4.3.28)

[Petr Vones]

Depends on whether you need USB virtualization or not. As for bluescreen, please attach minidump file(s) to the ticket. There is also setupapi.log file in Windows directory that might provide additional information.

I would also run chkdsk and sfc after a BSOD had occured because it may corrupt file system.

[Josk]

Replying to Petr Vones:

Depends on whether you need USB virtualization or not. As for bluescreen, please attach minidump file(s) to the ticket. There is also setupapi.log file in Windows directory that might provide additional information.

I would also run chkdsk and sfc after a BSOD had occured because it may corrupt file system.

I was able to install 4.3.26 again without problem by unchecking USB. I'l try 4.3.28 and let you know what happened

EDIT: As you can see with the attachment, I crashed during install. I was able to find minidump folder on Windows folder, but I didn't find the setupapi.log I runned CHKDSK and nothing went wrong. sfc /VERIFYONLY is running atm

[Josk]

Minidump file from bluescreen during 4.3.28 install(USB option checked)

[VVP]

I guess logic was following:

1. installation 4.3.28 caused BSOD.
2. installation 4.3.28 wasn't finished correctly, so there were some leftovers in the Windows registry related 4.3.28.
3. installation 4.3.26 failed because those leftovers from 4.3.28 had prevented to do it.

as advice: you should find 4.3.28 leftovers in the registry and manually delete them. for example see in: HKLM\software\microsoft\windows\current version\difx\driverstore HKLM\software\microsoft\windows\current version\difx\services HKLM\software\microsoft\windows\current version\difxapp

about BSOD, i'll take a look what happened there.

[VVP]

Forgot to ask, do you have 4.3.28 installation log when BSOD occurred?

[Josk]

MSI log when BSOD occurs

[Josk]

here is the log.

[Petr Vones]

The MSI log is incomplete but no wonder when a BSOD occured. The BSOD is DPC_WATCHDOG_VIOLATION related to mssmbios.sys. For a deep research ... ​http://blogs.msdn.com/b/ntdebugging/archive/2012/12/07/determining-the-source-of-bug-check-0x133-dpc-watchdog-violation-errors-on-windows-server-2012.aspx

[Josk]

I understand. So it seems that something you're doing in the driver is taking to much time. What can I do?