Win7 Pro (64) guest still fails to shutdown since 7.0.16
-
- Posts: 94
- Joined: 7. Mar 2016, 13:28
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: ArchLinux; Fedora; Ubuntu; Win7pro64; WinXP
- Contact:
Re: Win7 Pro (64) guest still fails to shutdown since 7.0.16
EDIT1: other unrelated problem prevalent at moment (re: segfault core dump in the log) with VirtualBox overall
EDIT2: dumb mistake, booted wrong kernel regarding EDIT1, the USB problem remains.
Re: Win7 Pro (64) guest still fails to shutdown since 7.0.16
I have been following the same path as @wfv but have slightly different experiences.
Firstly, disabling USB support seems to enable a clean start and shutdown. However, re-enabling USB2 results in Win7 hanging (and my touchpad actions in UBuntu being largely ineffective!) but right clicking on the VMbox icon prompts me to be able to 'stop the virtual machine'. Normal Ubuntu service then resumes.
As an aside, as a matter of course, I always have to mess about with the bridge adaptor in the network settings -swapping between the two available names and back again to gain internet access. I have got used to this other irritation but what was interesting is that with USB disabled, I did not have to do this at any time during my trials.
Do these two factors suggest there is something badly wrong with the USB support?
For further info, in addition to the latest VMbox, I am using both the latest guest additions and extension packs.
Also I am using a Dell laptop and built in touchpad and no external mouse.
Cheers, Chris D
Firstly, disabling USB support seems to enable a clean start and shutdown. However, re-enabling USB2 results in Win7 hanging (and my touchpad actions in UBuntu being largely ineffective!) but right clicking on the VMbox icon prompts me to be able to 'stop the virtual machine'. Normal Ubuntu service then resumes.
As an aside, as a matter of course, I always have to mess about with the bridge adaptor in the network settings -swapping between the two available names and back again to gain internet access. I have got used to this other irritation but what was interesting is that with USB disabled, I did not have to do this at any time during my trials.
Do these two factors suggest there is something badly wrong with the USB support?
For further info, in addition to the latest VMbox, I am using both the latest guest additions and extension packs.
Also I am using a Dell laptop and built in touchpad and no external mouse.
Cheers, Chris D
-
- Posts: 94
- Joined: 7. Mar 2016, 13:28
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: ArchLinux; Fedora; Ubuntu; Win7pro64; WinXP
- Contact:
Re: Win7 Pro (64) guest still fails to shutdown since 7.0.16
@ chrisd -
Network connection could be a different issue however, that you experience non-issue with network when USB2 is disabled is beyond my skill level (and i use that term exceedingly loosely for lack of better term ) - otherwise in reply to your question, yes something badly wrong with USB support for Win7 - don't know where Oracle has the code and commits since website changed recently to delve into deeper - bisect 7.0.14 vs 7.0.16 USB fixes.
Do these two factors suggest there is something badly wrong with the USB support?
Network connection could be a different issue however, that you experience non-issue with network when USB2 is disabled is beyond my skill level (and i use that term exceedingly loosely for lack of better term ) - otherwise in reply to your question, yes something badly wrong with USB support for Win7 - don't know where Oracle has the code and commits since website changed recently to delve into deeper - bisect 7.0.14 vs 7.0.16 USB fixes.
Re: Win7 Pro (64) guest still fails to shutdown since 7.0.16
@wfv
For info, I access the internet via Wifi connected dongle - so its not even USB!
However, I'll leave this issue as we're drifting off topic.
Chris
For info, I access the internet via Wifi connected dongle - so its not even USB!
However, I'll leave this issue as we're drifting off topic.
Chris
-
- Posts: 57
- Joined: 23. Mar 2011, 09:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows
Re: Win7 Pro (64) guest still fails to shutdown since 7.0.16
I believe that this is related to Virtualization Based Security - which is being heavily pushed by Microsoft. Microsoft are actually being so pushy, that even though you may got an MDM enterprise environment, then policies for disabling Virtualization Based Security only works on/off (got a ticket with Microsoft on that one).
There are two solutions for this:
Oracle should do a diff on the code between 7.0.14 and 7.0.16 - and locate the change between those versions that's triggering the problem. It's there for sure.
Or ..
Run the following commands on a daily basis - when all Hyper-V and other virtualization Windows-features has been disabled using the "Turn Windows features on or off" tool:
Running "msinfo" should look like this after the reboot, and then your VM's should shutdown without problems:
(while writing this post, I managed to do a complete installation of Windows 7 x64 - which would be impossible without running above commands)
There are two solutions for this:
Oracle should do a diff on the code between 7.0.14 and 7.0.16 - and locate the change between those versions that's triggering the problem. It's there for sure.
Or ..
Run the following commands on a daily basis - when all Hyper-V and other virtualization Windows-features has been disabled using the "Turn Windows features on or off" tool:
Code: Select all
@echo off
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set vsmlaunchtype off
bcdedit /set hypervisorlaunchtype off
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard /v EnableVirtualizationBasedSecurity /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard /v RequirePlatformSecurityFeatures /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard /v Enabled /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity /v Enabled /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\KernelShadowStacks /v Enabled /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\SystemGuard /v Enabled /t REG_DWORD /d 0 /f
start ms-settings:windowsdefender
set Message=Ensure that the following is disabled and then reboot the computer: Device security / Core isolation / Memory Integrity
echo.
echo %Message%
msg %username% %Message%
(while writing this post, I managed to do a complete installation of Windows 7 x64 - which would be impossible without running above commands)