Unable to launch WSL2 #4598
Comments
|
Is virtualization enabled in your computers bios? |
|
Yes. I'm able to run virtualbox. I do development on WSL2, It was working
fine until 3 days ago. So I had to switch back
to VirtualBox.
…On Tue, Oct 15, 2019 at 9:56 PM Ben Hillis ***@***.***> wrote:
Is virtualization enabled in your computers bios?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4598?email_source=notifications&email_token=AEJNJ6OAGUSRH4QGFBR7BCTQOXVK7A5CNFSM4JA3IQOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJMSTA#issuecomment-542296396>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJNJ6JXV4RKGPQE26AASYLQOXVK7ANCNFSM4JA3IQOA>
.
|
|
@amalshaji - Are there any interesting messages in any of the Hyper-V related eventvwr logs? |
|
Yes. Hyper-V-Hypervisor displays 3 warning messages around the date this
happened
************************************************************************************************************************************************************************************************************************************************************
Log Name: Microsoft-Windows-Hyper-V-Hypervisor-Operational
Source: Microsoft-Windows-Hyper-V-Hypervisor
Date: 09-10-2019 07:07:17 PM
Event ID: 12550
Task Category: None
Level: Warning
Keywords: (70368744177664)
User: SYSTEM
Computer: BEAST
Description:
Hyper-V detected access to a restricted MSR (Msr: 0x65C, IsWrite: 0x0,
MsrValue: 0xDD0000, AccessStatus: 0x0, Pc: 0xFFFFF807452C0200, ImageBase:
0xFFFFF807452B0000, ImageChecksum: 0x68C4F, ImageTimestamp: 0x59FB8DEC,
ImageName: esif_lf.sys).
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>12550</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000400000000000</Keywords>
<TimeCreated SystemTime="2019-10-09T13:37:17.270419200Z" />
<EventRecordID>2</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="484" />
<Channel>Microsoft-Windows-Hyper-V-Hypervisor-Operational</Channel>
<Computer>BEAST</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Msr">0x65c</Data>
<Data Name="IsWrite">0</Data>
<Data Name="MsrValue">0xdd0000</Data>
<Data Name="AccessStatus">0</Data>
<Data Name="Pc">0xfffff807452c0200</Data>
<Data Name="ImageBase">0xfffff807452b0000</Data>
<Data Name="ImageChecksum">0x68c4f</Data>
<Data Name="ImageTimestamp">0x59fb8dec</Data>
<Data Name="ImageName">esif_lf.sys</Data>
</EventData>
</Event>
************************************************************************************************************************************************************************************************************************************************************
Log Name: Microsoft-Windows-Hyper-V-Hypervisor-Operational
Source: Microsoft-Windows-Hyper-V-Hypervisor
Date: 10-10-2019 09:46:28 AM
Event ID: 12550
Task Category: None
Level: Warning
Keywords: (70368744177664)
User: SYSTEM
Computer: BEAST
Description:
Hyper-V detected access to a restricted MSR (Msr: 0x65C, IsWrite: 0x0,
MsrValue: 0xDD0000, AccessStatus: 0x0, Pc: 0xFFFFF8026CB60200, ImageBase:
0xFFFFF8026CB50000, ImageChecksum: 0x68C4F, ImageTimestamp: 0x59FB8DEC,
ImageName: esif_lf.sys).
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>12550</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000400000000000</Keywords>
<TimeCreated SystemTime="2019-10-10T04:16:28.253723500Z" />
<EventRecordID>5</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="428" />
<Channel>Microsoft-Windows-Hyper-V-Hypervisor-Operational</Channel>
<Computer>BEAST</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Msr">0x65c</Data>
<Data Name="IsWrite">0</Data>
<Data Name="MsrValue">0xdd0000</Data>
<Data Name="AccessStatus">0</Data>
<Data Name="Pc">0xfffff8026cb60200</Data>
<Data Name="ImageBase">0xfffff8026cb50000</Data>
<Data Name="ImageChecksum">0x68c4f</Data>
<Data Name="ImageTimestamp">0x59fb8dec</Data>
<Data Name="ImageName">esif_lf.sys</Data>
</EventData>
</Event>
************************************************************************************************************************************************************************************************************************************************************
Log Name: Microsoft-Windows-Hyper-V-Hypervisor-Operational
Source: Microsoft-Windows-Hyper-V-Hypervisor
Date: 10-10-2019 01:14:55 PM
Event ID: 12550
Task Category: None
Level: Warning
Keywords: (70368744177664)
User: SYSTEM
Computer: BEAST
Description:
Hyper-V detected access to a restricted MSR (Msr: 0x65C, IsWrite: 0x0,
MsrValue: 0xDD0000, AccessStatus: 0x0, Pc: 0xFFFFF8066B930200, ImageBase:
0xFFFFF8066B920000, ImageChecksum: 0x68C4F, ImageTimestamp: 0x59FB8DEC,
ImageName: esif_lf.sys).
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>12550</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000400000000000</Keywords>
<TimeCreated SystemTime="2019-10-10T07:44:55.233908400Z" />
<EventRecordID>8</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="9220" />
<Channel>Microsoft-Windows-Hyper-V-Hypervisor-Operational</Channel>
<Computer>BEAST</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Msr">0x65c</Data>
<Data Name="IsWrite">0</Data>
<Data Name="MsrValue">0xdd0000</Data>
<Data Name="AccessStatus">0</Data>
<Data Name="Pc">0xfffff8066b930200</Data>
<Data Name="ImageBase">0xfffff8066b920000</Data>
<Data Name="ImageChecksum">0x68c4f</Data>
<Data Name="ImageTimestamp">0x59fb8dec</Data>
<Data Name="ImageName">esif_lf.sys</Data>
</EventData>
</Event>
************************************************************************************************************************************************************************************************************************************************************
I hope this helps
…On Fri, Oct 18, 2019 at 4:29 AM Ben Hillis ***@***.***> wrote:
@amalshaji <https://github.com/amalshaji> - Are there any interesting
messages in any of the Hyper-V related eventvwr logs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4598?email_source=notifications&email_token=AEJNJ6PI3RTRIQ4LB4LZ2QDQPDU33A5CNFSM4JA3IQOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBRZNMA#issuecomment-543397552>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEJNJ6P5PFR5VDCBTIXW6B3QPDU33ANCNFSM4JA3IQOA>
.
|
|
Currently I'm on Windows Insider Version 18999 and downloading 19002.
Let me see if the update fixes the issue.
…On Fri, Oct 18, 2019 at 9:53 AM Amal Shaji ***@***.***> wrote:
Yes. Hyper-V-Hypervisor displays 3 warning messages around the date this
happened
************************************************************************************************************************************************************************************************************************************************************
Log Name: Microsoft-Windows-Hyper-V-Hypervisor-Operational
Source: Microsoft-Windows-Hyper-V-Hypervisor
Date: 09-10-2019 07:07:17 PM
Event ID: 12550
Task Category: None
Level: Warning
Keywords: (70368744177664)
User: SYSTEM
Computer: BEAST
Description:
Hyper-V detected access to a restricted MSR (Msr: 0x65C, IsWrite: 0x0,
MsrValue: 0xDD0000, AccessStatus: 0x0, Pc: 0xFFFFF807452C0200, ImageBase:
0xFFFFF807452B0000, ImageChecksum: 0x68C4F, ImageTimestamp: 0x59FB8DEC,
ImageName: esif_lf.sys).
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>12550</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000400000000000</Keywords>
<TimeCreated SystemTime="2019-10-09T13:37:17.270419200Z" />
<EventRecordID>2</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="484" />
<Channel>Microsoft-Windows-Hyper-V-Hypervisor-Operational</Channel>
<Computer>BEAST</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Msr">0x65c</Data>
<Data Name="IsWrite">0</Data>
<Data Name="MsrValue">0xdd0000</Data>
<Data Name="AccessStatus">0</Data>
<Data Name="Pc">0xfffff807452c0200</Data>
<Data Name="ImageBase">0xfffff807452b0000</Data>
<Data Name="ImageChecksum">0x68c4f</Data>
<Data Name="ImageTimestamp">0x59fb8dec</Data>
<Data Name="ImageName">esif_lf.sys</Data>
</EventData>
</Event>
************************************************************************************************************************************************************************************************************************************************************
Log Name: Microsoft-Windows-Hyper-V-Hypervisor-Operational
Source: Microsoft-Windows-Hyper-V-Hypervisor
Date: 10-10-2019 09:46:28 AM
Event ID: 12550
Task Category: None
Level: Warning
Keywords: (70368744177664)
User: SYSTEM
Computer: BEAST
Description:
Hyper-V detected access to a restricted MSR (Msr: 0x65C, IsWrite: 0x0,
MsrValue: 0xDD0000, AccessStatus: 0x0, Pc: 0xFFFFF8026CB60200, ImageBase:
0xFFFFF8026CB50000, ImageChecksum: 0x68C4F, ImageTimestamp: 0x59FB8DEC,
ImageName: esif_lf.sys).
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>12550</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000400000000000</Keywords>
<TimeCreated SystemTime="2019-10-10T04:16:28.253723500Z" />
<EventRecordID>5</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="428" />
<Channel>Microsoft-Windows-Hyper-V-Hypervisor-Operational</Channel>
<Computer>BEAST</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Msr">0x65c</Data>
<Data Name="IsWrite">0</Data>
<Data Name="MsrValue">0xdd0000</Data>
<Data Name="AccessStatus">0</Data>
<Data Name="Pc">0xfffff8026cb60200</Data>
<Data Name="ImageBase">0xfffff8026cb50000</Data>
<Data Name="ImageChecksum">0x68c4f</Data>
<Data Name="ImageTimestamp">0x59fb8dec</Data>
<Data Name="ImageName">esif_lf.sys</Data>
</EventData>
</Event>
************************************************************************************************************************************************************************************************************************************************************
Log Name: Microsoft-Windows-Hyper-V-Hypervisor-Operational
Source: Microsoft-Windows-Hyper-V-Hypervisor
Date: 10-10-2019 01:14:55 PM
Event ID: 12550
Task Category: None
Level: Warning
Keywords: (70368744177664)
User: SYSTEM
Computer: BEAST
Description:
Hyper-V detected access to a restricted MSR (Msr: 0x65C, IsWrite: 0x0,
MsrValue: 0xDD0000, AccessStatus: 0x0, Pc: 0xFFFFF8066B930200, ImageBase:
0xFFFFF8066B920000, ImageChecksum: 0x68C4F, ImageTimestamp: 0x59FB8DEC,
ImageName: esif_lf.sys).
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>12550</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000400000000000</Keywords>
<TimeCreated SystemTime="2019-10-10T07:44:55.233908400Z" />
<EventRecordID>8</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="9220" />
<Channel>Microsoft-Windows-Hyper-V-Hypervisor-Operational</Channel>
<Computer>BEAST</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Msr">0x65c</Data>
<Data Name="IsWrite">0</Data>
<Data Name="MsrValue">0xdd0000</Data>
<Data Name="AccessStatus">0</Data>
<Data Name="Pc">0xfffff8066b930200</Data>
<Data Name="ImageBase">0xfffff8066b920000</Data>
<Data Name="ImageChecksum">0x68c4f</Data>
<Data Name="ImageTimestamp">0x59fb8dec</Data>
<Data Name="ImageName">esif_lf.sys</Data>
</EventData>
</Event>
************************************************************************************************************************************************************************************************************************************************************
I hope this helps
On Fri, Oct 18, 2019 at 4:29 AM Ben Hillis ***@***.***>
wrote:
> @amalshaji <https://github.com/amalshaji> - Are there any interesting
> messages in any of the Hyper-V related eventvwr logs?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4598?email_source=notifications&email_token=AEJNJ6PI3RTRIQ4LB4LZ2QDQPDU33A5CNFSM4JA3IQOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBRZNMA#issuecomment-543397552>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AEJNJ6P5PFR5VDCBTIXW6B3QPDU33ANCNFSM4JA3IQOA>
> .
>
|
|
Updated to 19002. WSL2 working fine now. Please fix the issue on 18999. |
|
@amalshaji - We do not backport fixes to previous Windows Insider builds. Glad this is working for you now. |
|
@benhillis I'm on 19041 and still facing this issue 🤔 |
|
@nk521 If possible do a clean install of Windows, not from the backup or snapshot. |
2 tasks
This was referenced Feb 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please fill out the below information:
Your Windows build number: (Type
verat a Windows Command Prompt)Microsoft Windows [Version 10.0.18999.1]
What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
When I try to launch wsl, this is the output even though virtualization and WSL are enabled
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/wsl2-installscreenshot
What's wrong / what should be happening instead:
Strace of the failing command, if applicable: (If
some_commandis failing, then runstrace -o some_command.strace -f some_command some_args, and link the contents ofsome_command.stracein a gist here).For WSL launch issues, please collect detailed logs.
See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: