J
JinnKarr USA
HI all so i have the new release off 1903 installed it on the 21 build number 18362.116 and when i first installed it all worked great sandbox and all now windows sandbox opens but sits on its blue splash screen and does nothing at all? i see errors in the even viewer about rite protection and can't restore virtual system and stuff, but nothing of mine is write protected, i don't now hat it could be here are the error i see related to hyper-v worker. any help appreciated so i can use this feature again thanks and have a great night or day.
Log Name: Microsoft-Windows-Hyper-V-Worker-AdminSource: Microsoft-Windows-Hyper-V-WorkerDate: 5/22/2019 9:45:01 PMEvent ID: 12080Task Category: NoneLevel: ErrorKeywords: User: NT VIRTUAL MACHINE\5A76E41C-EBFB-437B-AC31-2FF933351597Computer: DESKTOP-8J2RS9LDescription:'Virtual Machine' Virtual SMB Device (Instance ID FEA6E63B-45DA-4E32-8B3D-1873B2CE50E7): Failed to restore with Error 'The media is write protected.' (0x80070013). (Virtual machine ID 5A76E41C-EBFB-437B-AC31-2FF933351597)Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51ddfa29-d5c8-4803-be4b-2ecb715570fe}" /> <EventID>12080</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2019-05-23T04:45:01.620069100Z" /> <EventRecordID>30</EventRecordID> <Correlation ActivityID="{ca88e720-1121-0006-78f5-88ca2111d501}" /> <Execution ProcessID="7472" ThreadID="7496" /> <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel> <Computer>DESKTOP-8J2RS9L</Computer> <Security UserID="S-1-5-83-1-1517741084-1132194811-4180619692-2534749491" /> </System> <UserData> <VmlEventLog xmlns="Explore Windows 10 OS, Computers, Apps, & More | Microsoft"> <VmName>Virtual Machine</VmName> <VmId>5A76E41C-EBFB-437B-AC31-2FF933351597</VmId> <DeviceName>Virtual SMB Device</DeviceName> <ErrorCodeString>%%2147942419</ErrorCodeString> <ErrorCode>0x80070013</ErrorCode> <DeviceInstanceId>FEA6E63B-45DA-4E32-8B3D-1873B2CE50E7</DeviceInstanceId> <Param1> </Param1> </VmlEventLog> </UserData></Event>
Log Name: SystemSource: Microsoft-Windows-Hyper-V-HypervisorDate: 5/24/2019 3:08:33 PMEvent ID: 157Task Category: NoneLevel: WarningKeywords: (70368744177664)User: SYSTEMComputer: DESKTOP-8J2RS9LDescription:The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Hyper-V-Hypervisor" Guid="{52fc89f8-995e-434c-a91e-199986449890}" /> <EventID>157</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000000</Keywords> <TimeCreated SystemTime="2019-05-24T22:08:33.746600300Z" /> <EventRecordID>1651</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>DESKTOP-8J2RS9L</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> </EventData></Event>
Continue reading...
Log Name: Microsoft-Windows-Hyper-V-Worker-AdminSource: Microsoft-Windows-Hyper-V-WorkerDate: 5/22/2019 9:45:01 PMEvent ID: 12080Task Category: NoneLevel: ErrorKeywords: User: NT VIRTUAL MACHINE\5A76E41C-EBFB-437B-AC31-2FF933351597Computer: DESKTOP-8J2RS9LDescription:'Virtual Machine' Virtual SMB Device (Instance ID FEA6E63B-45DA-4E32-8B3D-1873B2CE50E7): Failed to restore with Error 'The media is write protected.' (0x80070013). (Virtual machine ID 5A76E41C-EBFB-437B-AC31-2FF933351597)Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51ddfa29-d5c8-4803-be4b-2ecb715570fe}" /> <EventID>12080</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2019-05-23T04:45:01.620069100Z" /> <EventRecordID>30</EventRecordID> <Correlation ActivityID="{ca88e720-1121-0006-78f5-88ca2111d501}" /> <Execution ProcessID="7472" ThreadID="7496" /> <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel> <Computer>DESKTOP-8J2RS9L</Computer> <Security UserID="S-1-5-83-1-1517741084-1132194811-4180619692-2534749491" /> </System> <UserData> <VmlEventLog xmlns="Explore Windows 10 OS, Computers, Apps, & More | Microsoft"> <VmName>Virtual Machine</VmName> <VmId>5A76E41C-EBFB-437B-AC31-2FF933351597</VmId> <DeviceName>Virtual SMB Device</DeviceName> <ErrorCodeString>%%2147942419</ErrorCodeString> <ErrorCode>0x80070013</ErrorCode> <DeviceInstanceId>FEA6E63B-45DA-4E32-8B3D-1873B2CE50E7</DeviceInstanceId> <Param1> </Param1> </VmlEventLog> </UserData></Event>
Log Name: SystemSource: Microsoft-Windows-Hyper-V-HypervisorDate: 5/24/2019 3:08:33 PMEvent ID: 157Task Category: NoneLevel: WarningKeywords: (70368744177664)User: SYSTEMComputer: DESKTOP-8J2RS9LDescription:The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Hyper-V-Hypervisor" Guid="{52fc89f8-995e-434c-a91e-199986449890}" /> <EventID>157</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000000</Keywords> <TimeCreated SystemTime="2019-05-24T22:08:33.746600300Z" /> <EventRecordID>1651</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>DESKTOP-8J2RS9L</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> </EventData></Event>
Continue reading...