W10 bleibt bei start stehen

Allgemeine Diskussionen über den Einsatz von VirtualBox.
Post Reply
MR_Itzum
Posts: 3
Joined: 6. Jan 2020, 13:06

W10 bleibt bei start stehen

Post by MR_Itzum »

Hallo zusammen,
ich habe heute Morgen ein Bios-Update an meinem Laptop (DELL 5500) durchgeführt und seit dem lässt sich meine VM (Version 6.1.0) mit W10 nicht mehr starten. Es wird ein schwarzer Bildschirm mit dem türkisfarbenen Windows-Logo angezeigt und der Lüfter des Laptop zeigt an, dass scheinbar etwas passiert, aber es passiert nichts mehr. Letzte Woche lief alles noch völlig normal.

VG
MR_ITZUM
Attachments
W10-2020-01-06-11-51-43.zip
(20.05 KiB) Downloaded 25 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: W10 bleibt bei start stehen

Post by mpack »

Answering in English.

Perhaps the BIOS update disabled VT-x/AMD-v.
 Edit: . No, that doesn't seem to be it. In fact I'm struggling to see any problem in your log. The VM boots and loads the Guest Additions.

Perhap try it with 3D acceleration disabled. If this works then it implies a hardening problem with a host graphics driver.

[Edit2]. In fact I can confirm that you have a hardening problem due to some unsigned shell extension you have installed. Odd that it installs into the "Program Files (x86)" folder but still injects 64bit DLLs into running programs.
00:04:02.575368 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume3\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll: Not signed.
00:04:02.575495 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll' (C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll): rcNt=0xc0000190
00:04:02.576258 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume3\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll
00:04:02.576290 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll' (C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll): rcNt=0xc0000190
00:04:02.576878 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=2 \Device\HarddiskVolume3\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll
00:04:02.576909 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll' (C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll): rcNt=0xc0000190
00:04:02.577491 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=3 \Device\HarddiskVolume3\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll
00:04:02.577522 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll' (C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll): rcNt=0xc0000190
00:04:02.578119 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=4 \Device\HarddiskVolume3\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll
00:04:02.578162 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll' (C:\Program Files (x86)\ownCloud\shellext_x64\OCOverlays.dll): rcNt=0xc0000190
00:04:02.804226 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_ASN1_CURSOR_ILLEGAL_CONSTRUCTED_STRING fImage=1 fProtect=0xf0005 fAccess=0x2 \Device\HarddiskVolume3\Program Files\Intel\OptaneShellExtensions\OptaneShellExt.dll: WinCert.CI.Content.SignedData.Certificates.u.pX509Cert.TbsCertificate.T3.Extensions.papItems[#].ExtnValue.NameConstraints.T0.PermittedSubtrees.papItems[#]: Unexpected sequence type/flags: 0x1/0x80 (expected 0x10/0x20): \Device\HarddiskVolume3\Program Files\Intel\OptaneShellExtensions\OptaneShellExt.dll
00:04:02.805558 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_SUP_VP_NOT_OWNED_BY_TRUSTED_INSTALLER fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume3\Users\Markus Renner\AppData\Local\Microsoft\OneDrive\19.192.0926.0012\amd64\FileSyncShell64.dll: supHardenedWinVerifyImageByHandle: TrustedInstaller is not the owner of '\Device\HarddiskVolume3\Users\Markus Renner\AppData\Local\Microsoft\OneDrive\19.192.0926.0012\amd64\FileSyncShell64.dll'.
 
MR_Itzum
Posts: 3
Joined: 6. Jan 2020, 13:06

Re: W10 bleibt bei start stehen

Post by MR_Itzum »

Thanks for your reply
I have now installed version 6.0.2 and everything works again :D
sb1
Posts: 5
Joined: 4. Jan 2014, 04:52

Re: W10 bleibt bei start stehen

Post by sb1 »

MR_Itzum wrote:Thanks for your reply
I have now installed version 6.0.2 and everything works again :D
I had the same problem: I had version 6.1.0 installed. After changing my motherboard, a W10 client VM hung during booting.
Now i have downgraded to version 6.02 and the VM is running again. Version 6.1.x is still buggy
Thank you for the hint. :D
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: W10 bleibt bei start stehen

Post by mpack »

The above discussion is not evidence of a bug, it's evidence of questionable software being installed on the host by the user. All VirtualBox did was detect it, and going back to a weaker version of hardening is not really a long term solution.
sb1
Posts: 5
Joined: 4. Jan 2014, 04:52

Re: W10 bleibt bei start stehen

Post by sb1 »

mpack wrote:The above discussion is not evidence of a bug, it's evidence of questionable software being installed on the host by the user. All VirtualBox did was detect it, and going back to a weaker version of hardening is not really a long term solution.
Hello mpack,
The same VM works on different engines without trouble. After changing the Bios or motherboard then the trouble begins. If the Virtualbox version is downgraded then the VM will run again with the new bios or new motherboard.
If i start the same VM on an engine with an older bios (DELL notebook) but with the new VB version, then i will work also.
The new motherboard in the desktop-Pc is from MSI (Z390A PRO and AMI-Bios) and not from DELL.

This seems to me, that the newer VB has a problem with current bios versions.
sb1
Posts: 5
Joined: 4. Jan 2014, 04:52

Re: W10 bleibt bei start stehen

Post by sb1 »

After waiting some versions, I have now tried version 6.1.4 and it works again.
They found the bug. :D :D
Post Reply