[WorksForMe] Hardening Error caused by Window 10 Update KB4284835.

[Stokesay]

Hi,

Hope you can help.

My VirtualBox has stopped working after the installation of update KB4284835.

I get the error:

supr3hardenedrespawn what: 5 verr_invalid_name (-104) - Invalid (malformed) file/path name.

.. on trying to start a VM followed by:

Failed to open a session for the virtual machine PB11 Dev.

The virtual machine 'PB11 Dev' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Steve\VirtualBox VMs\PB11 Dev\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}.

Here are the details of my OS/Software:

VirtualBox Version 5.2.12 r122591 (Qt5.6.2)

OS : Microsoft Windows 10 Pro Version : 10.0.17134 Build 17134

Antivirus: Avast Free Version 18.4.2338 (build 18.4.3895.327)

So far:

1. I uninstalled Avast, Update KB4284835, and VirtualBox.
2. Rebooted.
3. Reinstalled VirtualBox and Additions (as Admin).
4. It works.
5. Machine auto-installed KB4284835 and rebooted.
6. It stops working again with the same error.
10. Uninstalled KB4284835 and VirtualBox again.
11. Reinstalled VirtualBox and Additions (as Admin).
12. It works.
13. Reinstalled Avast.
14. Rebooted.
15. It still works.
16. Machine auto-installed KB4284835 and rebooted.
17. It stops working again with the same error.
18. Uninstalled KB4284835 and VirtualBox again.
19. Reinstalled VirtualBox and Additions (as Admin).
20. It works.

The problem I have now is that I can only pause windows updates for 30 days, before the update re-installs.
I've tried using the windows wushowhide.diagcab tool to hide the update, but this no longer appears to work.

I've also followed various other related threads, such as delaying vboxdrv start (topic 82277) to no avail.

Note that I have another machine with VirtualBox on WIndows 10, with Avast and patch KB4284835, and it works OK still.

I've included the hardening log from when the error first occured. This, therefore, does make mention of Avast!

I've noticed I'm not alone in getting this error recently!

Any help most appreciated!

Steve.

[andyp73]

I think it would be more useful to have seen a log when Avast was uninstalled and KB4284835 was installed so we could see if there was anything the Windows update had screwed up. It may not be something being loaded that is conflicted it may be the certificate database is getting mangled.

-Andy.

[socratis]

Or actually 2 logs, both of them with Avast uninstalled; one with KB4284835 installed, one with it uninstalled.

[Stokesay]

OK. Will do! Something for the weekend!

[PeteThePen1]

Hi

May I add a similar story to that of Stokesay but lacking the joy of having VB work with either Avast or KB4284835 removed.

I was running VB 5.2.4-119785 prior to the Win 10 update but when it failed I upgraded to 5.2.12-122591. However that did not work either but at least it gave the same error message.

The PC is 64 bit, running Win 10 Home 1803 version 17134.113. Avast is version 18.4.2338.

I have attached three logs Zipped into one file. The first was before the removal of Avast and the Win 10 update and the second was after Avast and Win 10 were removed and the third was after Avast was put back. The possibly troublesome KB4284835 has, interestingly, failed to re-install despite Win 10 trying.

Many thanks for your support.

Pete

VBoxHardeningPFCAll.zip

(35.62 KiB) Downloaded 77 times

EDIT: I have just spotted the post on Hardening Issues in which the advice is to uninstall IBM's "Trusteer Endpoint Protection". This was pushed out by a lot of banks in the early days of on-line banking so lots of us will have it. Now it is uninstalled VB works as it always has done.

Regards

Pete

[socratis]

the advice is to uninstall IBM's "Trusteer Endpoint Protection" ... Now it is uninstalled VB works as it always has done.

Thanks for that update/edit, you just saved me from going through 3 different VBoxHardening.logs...

[Stokesay]

Hi,

Attached are multiple logs as requested. I've included logs at each stage of my testing (Note machine was restarted between each action):

Log 1. Started with working VBox with Avast Installed but not KB4284835. (With Avast, No KB4284835)
Log 2. Removed Avast and Restarted. Vbox Fails! I didn't expect this. (No Avast, No KB4284835)
Log 3. Reinstalled VBox. Works. (No Avast, No KB4284835)
Log 4. Installed KB4284835. Reinstalled VBox. Works! I didn't expect this. (No Avast, With KB4284835)
Log 5. Restart Machine again and re-try! Fails. (No Avast, With KB4284835)
Log 6. Removed KB4284835. Reinstalled VBox. Works. (No Avast, No KB4284835)
Log 7. Reinstalled Avast! Didn't reinstall vBbox. Fails! I didn't expect this. (With Avast, No KB4284835)
Log 8. Reinstalled VBox. Still Fails! I didn't expect this. (No Avast, No KB4284835)
Log 9. Removed Avast. Reinstalled VBox. Works. (No Avast, No KB4284835)

The net result is that Vbox now only works without Avast or KB4284835, despite working with Avast at the start of testing.

The only other thing to note is that I get the following message each time I remove and reinstall vBox (only on re installation):

Cannot rename this connection. A connection with the name that you specified already exists. Specify a different name.

Thank you!

[Stokesay]

STOP! After spotting last post, I noticed I also have IBM's "Trusteer Endpoint Protection". Just removing and reinstalling everything else to see what happens! I'll keep you posted.

[Stokesay]

Bingo! Trusteer Endpoint Protection removed. Avasted and KB4284835 installed. All working.

Working Log attached for completeness.

Thank you Pete for mentioning that.

[socratis]

Bingo! Trusteer Endpoint Protection removed. Avasted and KB4284835 installed. All working.

Thanks for the feedback. I'll mark the thread as [WorksForMe] so that anyone that stumbles upon the title won't get the wrong idea.