Wsl ошибка 0x1bc

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

nathanaelg opened this issue

Jul 25, 2020

· 42 comments

Comments

@nathanaelg

Environment

Windows build number: 10.0.19041.0

Steps to reproduce

Attempting to update to WSL2 after updating to Windows 10 2004. Following the instructions in https://docs.microsoft.com/en-us/windows/wsl/install-win10 when I get to setting WSL2 as default:

Expected behavior

Actual behavior

I get the following error code:

PS C:WINDOWSsystem32> wsl --set-default-version 2
Error: 0x1bc
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
kanlukasz, goa1bit, cderv, marius-turtle, bburket, oke-aditya, fresheneesz, justyns, CaliforniaMountainSnake, YvZheng, and 85 more reacted with thumbs up emoji
ssalbdivad, oke-aditya, liuliangsir, mrbiggleswirth, mztriz, and bhudd reacted with eyes emoji

@therealkenc

@Tealons

oising, CarlosLoriaSaenz, tretyakov-d, sankemax, 0xCiBeR, Empreintes, seaswalker, gerardbosch, cokeplus, ivang7, and 167 more reacted with thumbs up emoji
jjjacques, Mr-MooMoo, artogahr, and 0x0bloodyknight reacted with laugh emoji
saidnamyzO, liuliangsir, jonrosner, dbones, barfin, wefewwe211321, chtenb, laurent22, sugaith, mrbiggleswirth, and 10 more reacted with hooray emoji
cokeplus, tomresing, arnowelzel, Zaczero, Arnaud15, Akimace, visoks2, justyns, liuliangsir, jonrosner, and 24 more reacted with heart emoji
jsejcksn and 0x0bloodyknight reacted with rocket emoji

@oising

Came here to report the same error (sb3 — setting default version to 2 after having enabled vmp)

update: can confirm that updating the kernel corrected the problem. Obviously I am running 2004 (for anyone reading)

sankemax, dandar3, justyns, liuliangsir, xRager, ayyar, Jc51aT, amolg98, nielsabels, patchie, and 10 more reacted with thumbs up emoji

@nathanaelg

I have tried running the kernel update but just get «This update only applies to machines with the Windows Subsystem for Linux». WSL1 still seems to be working fine.

image

I have collected detailed logs, should these be submitted here or through the secure@microsoft.com? Would they contain any private details?

@jylilaht

I have tried running the kernel update but just get «This update only applies to machines with the Windows Subsystem for Linux». WSL1 still seems to be working fine.

I have collected detailed logs, should these be submitted here or through the secure@microsoft.com? Would they contain any private details?

I HAD this same problem. Updated windows build, wsl2 kernel, disabled hyper-v, enabled virtualization and wsl. WSL update give s this error message and does not install.

Solved my issue. You need to go right click .msi installer file and uninstall. Then install again. Like told in first note here: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

dennis-garavsky, maligang, ADD-SP, moerketh, oguimbal, gvee-uk, slcho1, Nakilon, tkmcmaster, gindulis, and 61 more reacted with thumbs up emoji
LPrimahatva, liuliangsir, joe-sm, wude935, jiaton, luka-bacic, Silventino, rvajustin, escape0707, firephreek, and 5 more reacted with hooray emoji
oguimbal, gvee-uk, psxvoid, pirtim, monsona, OtterBoops, liuliangsir, wude935, jiaton, luka-bacic, and 10 more reacted with heart emoji
oguimbal, gvee-uk, psxvoid, monsona, liuliangsir, wude935, jiaton, Silventino, rvajustin, paul2ma, and 7 more reacted with rocket emoji

@Tealons

Maybe also good to mention was that some restarting was required during the process, but this is not very well documented. I found this out the hard way :)

@nathanaelg

I have tried both restarting and uninstalling (which failed, it said it wasn’t installed).

image

@dennis-garavsky

tomresing, KenMwaura1, tkmcmaster, bshea5, ghuser22, liuliangsir, F34th3R, mfreiholz, Arachin, Unkrass, and 7 more reacted with thumbs up emoji

@nathanaelg

Detailed logs:
lxcore.zip

@therealkenc Can I do anything more to progress this? Are the detailed logs captured correctly?

@ageprocpp

@lpabon

Ok, I have resolved my issue. This is what I did and one of the following models could have resolved it:

  1. Removed wsl and the vm additions
  2. rebooted
  3. Updated Windows 10 2004 with «Cumulative Update Preview for Windows 10 2004…» KB4568831 (Some how it picked this up when I clicked Check for updates).
  4. Right clicked on wsl_update_x64.msi kernel to uninstall
  5. Added wsl and vm additions
  6. rebooted
  7. Installed wsl_update_x64.msi kernel
  8. THEN I typed wsl --set-default-version 2 and it worked!

@charfole

@hariharan382

for me also same problem, did all the above steps still same result

@web-assistant

@tsubakimoto

I had the same problem. I was able to solve it by the method written by @web-assistant .

@hariharan382

did the same as in the link but could not update from wsl 1 to wsl2

@MallocArray

I had the same error message which ultimately lead me here. The Kernel update resolved it for me.

@therealkenc

Needs-investigation as the OP submission is effectively blocked on:

Solved my issue. You need to go right click .msi installer file and uninstall. Then install again. Like told in first note here: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

I have tried both restarting and uninstalling (which failed, it said it wasn’t installed).

(plus a side order of #5686)

@geekyarthurs

@headius

Seems like we have workarounds from @lpabon and @web-assistant but this error message is obviously terrible. Perhaps the work to be done at this point is to make it say something useful, perhaps recommending the kernel update or pointing to a FAQ or walkthrough that explains the workaround?

FWIW I could not get the update to install until I uninstalled it and started over as in @lpabon comment. It kept telling me it was only for systems with WSL until I removed it and went through the full process again.

@alexhiggins732

@nathanaelg

This was resolved (I believe) by a software update, I am not sure which one/s (potentially Windows Subsystem for Linux Update — 4.19.104 or 2020-08 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4566782)?)

@sbtcoles

@alexhiggins732

@nathanaelg The prior update does not show in my update history and KB4566782 is available for me to install, so neither addressed my issue, but they might prevent it in the future.

@ApfelkuchenHaus

@nathanaelg not true. I tried this today and got the error.

@darktohka

Still happened today, with all software updates installed.

Kernel update MSI resolved the problem.

@mark-stopka

Still happened today, with all software updates installed.

Kernel update MSI resolved the problem.

Same…

@long-nguyenxuan

This was resolved (I believe) by a software update, I am not sure which one/s (potentially Windows Subsystem for Linux Update — 4.19.104 or 2020-08 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4566782)?)

System up to date at 2020-08-17 07:31 but it still error :'(
image

@long-nguyenxuan

This was resolved (I believe) by a software update, I am not sure which one/s (potentially Windows Subsystem for Linux Update — 4.19.104 or 2020-08 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4566782)?)

System up to date at 2020-08-17 07:31 but it still error :'(

update:
restart and reinstall wsl2 kernel update make it works, magic!! 😂

@drk-mtr

Just experienced this on a brand new PC with a fresh Windows install, on version 2004, with updates checked today 19/08/2020. the resolution was as described i.e. install the kernel update — thanks for sharing the fix.

@ghost

Why should I install an add-on package for WSL 2 to work?

@long-nguyenxuan

Why should I install an add-on package for WSL 2 to work?

because it’s 2, and it requires an add-on package to work, if you don’t want to install addons package, feel free to stay with 1

@MuditJ

@dalenoe

Also seeing this issue.. haven’t got it resolved yet.

Resolved by removing the wsl2 update and reinstalling it.

@gahstanz

Hey guys,

After installing the wsl2-kernel a bit too hasty, I was receiving the same error mentioned. I was instructed to install the kernel update but received the «This update only applies to machines with the Windows Subsystem for Linux» error. If you’ve already done this like me then I’d assume you’ve already downloaded the kernel update and done the same.

I was able to resolve this by doing the following:

  1. Download the WSL 2 Kernel Update from the following link (this will download wsl_update_x64.msi):
    https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

  2. If you try to run this, you’ll get the WSL error as mentioned above. Right click on the downloaded wsl_update_x64.msi, select «Uninstall«.

  3. Once completed, I reinstalled the wsl_update_x64.msi successully and no without receiving the following error «This update only applies to machines with the Windows Subsystem for Linux«.

  4. Open Powershell as Administrator, and set the version to WSL 2 by typing in the following.
    wsl --set-default-version 2

You should no longer get the error.
image

@ThermoMan

The msi installer fixed my problem too. No other fix steps were required.

@saad-gh

I just had the same problem. Updating the WSL2 kernel (https://docs.microsoft.com/nl-nl/windows/wsl/wsl2-kernel) fixed it.
There is information in the documentation about a possible kernel error, but it seems that the error message is somehow broken?

This fix worked for me as well

@ruant

Why is the kernel installation poping up as Publisher: Unknown?
Isn’t this a Microsoft made file? (Signature says so..)

Maybe it’s just my computer and it’s CA that’s borked?

@therealkenc

Maybe it’s just my computer and it’s CA that’s borked?

That’s #5628, you aren’t alone. And yes it’s weird (and remains unexplained) because the file itself appears kosher.

@ManoloMoraes

Solved my issue. You need to go right click .msi installer file and uninstall. Then install again. Like told in first note here: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

Thank you, uninstall and install wsl_update_x64.msi solved my first problem, other problem solved enable virtualization on BIOS.

@amitai

The above suggestions did not fix my issue! :( I am still having a problem.

Like others above, I attemped to uninstall wsl_update_x64.msi. However, I get the error:

This action is only valid for products that are currently installed.

According to the FAQ on this error it could be one of these:

  1. My Windows version not supporting WSL2? Not the case: Windows 10 v2004 build 19041.450.
  2. WSL not enabled? Not the case: I see it is checked in turn features on or off. When I run wsl.exe it says I have no distros installed… but the command clearly runs (and I can’t install any distros because it says I need the kernel update)
  3. Reboot required? I rebooted.

@moditpro365

Help! I have uninstalled and reinstalled WSL components. The kernel update appears to install successfully. But when I try to set version 2 as default it tells me that the update is required. I have uninstalled and reinstalled the update. I get no errors. I’ve rebooted multiple times. Any assistance would be greatly appreciated. I’m racking my brain.

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

nathanaelg opened this issue

Jul 25, 2020

· 42 comments

Comments

@nathanaelg

Environment

Windows build number: 10.0.19041.0

Steps to reproduce

Attempting to update to WSL2 after updating to Windows 10 2004. Following the instructions in https://docs.microsoft.com/en-us/windows/wsl/install-win10 when I get to setting WSL2 as default:

Expected behavior

Actual behavior

I get the following error code:

PS C:WINDOWSsystem32> wsl --set-default-version 2
Error: 0x1bc
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
kanlukasz, goa1bit, cderv, marius-turtle, bburket, oke-aditya, fresheneesz, justyns, CaliforniaMountainSnake, YvZheng, and 85 more reacted with thumbs up emoji
ssalbdivad, oke-aditya, liuliangsir, mrbiggleswirth, mztriz, and bhudd reacted with eyes emoji

@therealkenc

@Tealons

oising, CarlosLoriaSaenz, tretyakov-d, sankemax, 0xCiBeR, Empreintes, seaswalker, gerardbosch, cokeplus, ivang7, and 167 more reacted with thumbs up emoji
jjjacques, Mr-MooMoo, artogahr, and 0x0bloodyknight reacted with laugh emoji
saidnamyzO, liuliangsir, jonrosner, dbones, barfin, wefewwe211321, chtenb, laurent22, sugaith, mrbiggleswirth, and 10 more reacted with hooray emoji
cokeplus, tomresing, arnowelzel, Zaczero, Arnaud15, Akimace, visoks2, justyns, liuliangsir, jonrosner, and 24 more reacted with heart emoji
jsejcksn and 0x0bloodyknight reacted with rocket emoji

@oising

Came here to report the same error (sb3 — setting default version to 2 after having enabled vmp)

update: can confirm that updating the kernel corrected the problem. Obviously I am running 2004 (for anyone reading)

sankemax, dandar3, justyns, liuliangsir, xRager, ayyar, Jc51aT, amolg98, nielsabels, patchie, and 10 more reacted with thumbs up emoji

@nathanaelg

I have tried running the kernel update but just get «This update only applies to machines with the Windows Subsystem for Linux». WSL1 still seems to be working fine.

image

I have collected detailed logs, should these be submitted here or through the secure@microsoft.com? Would they contain any private details?

@jylilaht

I have tried running the kernel update but just get «This update only applies to machines with the Windows Subsystem for Linux». WSL1 still seems to be working fine.

I have collected detailed logs, should these be submitted here or through the secure@microsoft.com? Would they contain any private details?

I HAD this same problem. Updated windows build, wsl2 kernel, disabled hyper-v, enabled virtualization and wsl. WSL update give s this error message and does not install.

Solved my issue. You need to go right click .msi installer file and uninstall. Then install again. Like told in first note here: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

dennis-garavsky, maligang, ADD-SP, moerketh, oguimbal, gvee-uk, slcho1, Nakilon, tkmcmaster, gindulis, and 61 more reacted with thumbs up emoji
LPrimahatva, liuliangsir, joe-sm, wude935, jiaton, luka-bacic, Silventino, rvajustin, escape0707, firephreek, and 5 more reacted with hooray emoji
oguimbal, gvee-uk, psxvoid, pirtim, monsona, OtterBoops, liuliangsir, wude935, jiaton, luka-bacic, and 10 more reacted with heart emoji
oguimbal, gvee-uk, psxvoid, monsona, liuliangsir, wude935, jiaton, Silventino, rvajustin, paul2ma, and 7 more reacted with rocket emoji

@Tealons

Maybe also good to mention was that some restarting was required during the process, but this is not very well documented. I found this out the hard way :)

@nathanaelg

I have tried both restarting and uninstalling (which failed, it said it wasn’t installed).

image

@dennis-garavsky

tomresing, KenMwaura1, tkmcmaster, bshea5, ghuser22, liuliangsir, F34th3R, mfreiholz, Arachin, Unkrass, and 7 more reacted with thumbs up emoji

@nathanaelg

Detailed logs:
lxcore.zip

@therealkenc Can I do anything more to progress this? Are the detailed logs captured correctly?

@ageprocpp

@lpabon

Ok, I have resolved my issue. This is what I did and one of the following models could have resolved it:

  1. Removed wsl and the vm additions
  2. rebooted
  3. Updated Windows 10 2004 with «Cumulative Update Preview for Windows 10 2004…» KB4568831 (Some how it picked this up when I clicked Check for updates).
  4. Right clicked on wsl_update_x64.msi kernel to uninstall
  5. Added wsl and vm additions
  6. rebooted
  7. Installed wsl_update_x64.msi kernel
  8. THEN I typed wsl --set-default-version 2 and it worked!

@charfole

@hariharan382

for me also same problem, did all the above steps still same result

@web-assistant

@tsubakimoto

I had the same problem. I was able to solve it by the method written by @web-assistant .

@hariharan382

did the same as in the link but could not update from wsl 1 to wsl2

@MallocArray

I had the same error message which ultimately lead me here. The Kernel update resolved it for me.

@therealkenc

Needs-investigation as the OP submission is effectively blocked on:

Solved my issue. You need to go right click .msi installer file and uninstall. Then install again. Like told in first note here: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

I have tried both restarting and uninstalling (which failed, it said it wasn’t installed).

(plus a side order of #5686)

@geekyarthurs

@headius

Seems like we have workarounds from @lpabon and @web-assistant but this error message is obviously terrible. Perhaps the work to be done at this point is to make it say something useful, perhaps recommending the kernel update or pointing to a FAQ or walkthrough that explains the workaround?

FWIW I could not get the update to install until I uninstalled it and started over as in @lpabon comment. It kept telling me it was only for systems with WSL until I removed it and went through the full process again.

@alexhiggins732

@nathanaelg

This was resolved (I believe) by a software update, I am not sure which one/s (potentially Windows Subsystem for Linux Update — 4.19.104 or 2020-08 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4566782)?)

@sbtcoles

@alexhiggins732

@nathanaelg The prior update does not show in my update history and KB4566782 is available for me to install, so neither addressed my issue, but they might prevent it in the future.

@ApfelkuchenHaus

@nathanaelg not true. I tried this today and got the error.

@darktohka

Still happened today, with all software updates installed.

Kernel update MSI resolved the problem.

@mark-stopka

Still happened today, with all software updates installed.

Kernel update MSI resolved the problem.

Same…

@long-nguyenxuan

This was resolved (I believe) by a software update, I am not sure which one/s (potentially Windows Subsystem for Linux Update — 4.19.104 or 2020-08 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4566782)?)

System up to date at 2020-08-17 07:31 but it still error :'(
image

@long-nguyenxuan

This was resolved (I believe) by a software update, I am not sure which one/s (potentially Windows Subsystem for Linux Update — 4.19.104 or 2020-08 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4566782)?)

System up to date at 2020-08-17 07:31 but it still error :'(

update:
restart and reinstall wsl2 kernel update make it works, magic!! 😂

@drk-mtr

Just experienced this on a brand new PC with a fresh Windows install, on version 2004, with updates checked today 19/08/2020. the resolution was as described i.e. install the kernel update — thanks for sharing the fix.

@ghost

Why should I install an add-on package for WSL 2 to work?

@long-nguyenxuan

Why should I install an add-on package for WSL 2 to work?

because it’s 2, and it requires an add-on package to work, if you don’t want to install addons package, feel free to stay with 1

@MuditJ

@dalenoe

Also seeing this issue.. haven’t got it resolved yet.

Resolved by removing the wsl2 update and reinstalling it.

@gahstanz

Hey guys,

After installing the wsl2-kernel a bit too hasty, I was receiving the same error mentioned. I was instructed to install the kernel update but received the «This update only applies to machines with the Windows Subsystem for Linux» error. If you’ve already done this like me then I’d assume you’ve already downloaded the kernel update and done the same.

I was able to resolve this by doing the following:

  1. Download the WSL 2 Kernel Update from the following link (this will download wsl_update_x64.msi):
    https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

  2. If you try to run this, you’ll get the WSL error as mentioned above. Right click on the downloaded wsl_update_x64.msi, select «Uninstall«.

  3. Once completed, I reinstalled the wsl_update_x64.msi successully and no without receiving the following error «This update only applies to machines with the Windows Subsystem for Linux«.

  4. Open Powershell as Administrator, and set the version to WSL 2 by typing in the following.
    wsl --set-default-version 2

You should no longer get the error.
image

@ThermoMan

The msi installer fixed my problem too. No other fix steps were required.

@saad-gh

I just had the same problem. Updating the WSL2 kernel (https://docs.microsoft.com/nl-nl/windows/wsl/wsl2-kernel) fixed it.
There is information in the documentation about a possible kernel error, but it seems that the error message is somehow broken?

This fix worked for me as well

@ruant

Why is the kernel installation poping up as Publisher: Unknown?
Isn’t this a Microsoft made file? (Signature says so..)

Maybe it’s just my computer and it’s CA that’s borked?

@therealkenc

Maybe it’s just my computer and it’s CA that’s borked?

That’s #5628, you aren’t alone. And yes it’s weird (and remains unexplained) because the file itself appears kosher.

@ManoloMoraes

Solved my issue. You need to go right click .msi installer file and uninstall. Then install again. Like told in first note here: https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel

Thank you, uninstall and install wsl_update_x64.msi solved my first problem, other problem solved enable virtualization on BIOS.

@amitai

The above suggestions did not fix my issue! :( I am still having a problem.

Like others above, I attemped to uninstall wsl_update_x64.msi. However, I get the error:

This action is only valid for products that are currently installed.

According to the FAQ on this error it could be one of these:

  1. My Windows version not supporting WSL2? Not the case: Windows 10 v2004 build 19041.450.
  2. WSL not enabled? Not the case: I see it is checked in turn features on or off. When I run wsl.exe it says I have no distros installed… but the command clearly runs (and I can’t install any distros because it says I need the kernel update)
  3. Reboot required? I rebooted.

@moditpro365

Help! I have uninstalled and reinstalled WSL components. The kernel update appears to install successfully. But when I try to set version 2 as default it tells me that the update is required. I have uninstalled and reinstalled the update. I get no errors. I’ve rebooted multiple times. Any assistance would be greatly appreciated. I’m racking my brain.

Windows 10 users might receive the following error when trying to set WSL 2 as the default Windows Subsystem for Linux.

wsl --set-default-version 2
WSL 2 requires an update to its kernel component.

Or the following on VirtualBox:

Error: 0x1bc

We can easily fix this error by installing the WSL Linux kernel update on Windows 10. To do that, click on the following link: https://wslstorestorage.blob.core.windows.net/wslblob/wsl_update_x64.msi to download the WSL2 Linux kernel update.

Once the download is complete, double-click the «wsl_update_x64.msi» file to run and apply kernel updates.

WSL 2 requires an update to its kernel component

After that, you should be able to change Windows Subsystem for Linux to Version 2 without getting an error.

Upgrade to Windows 10 2004 May 2020 update brought out multiple issues such as Bluetooth not working, BSOD, Data deletion bug. Some users encounter Error 0x1bc when updating Windows Subsystem for Linux after installing the update.

Error 0x1bc occurs when you try to update WSL 2 after updating Windows 10 to v2004 and the message is – “PS C:WINDOWSsystem32> wsl –set-default-version 2 Error: 0x1bc”. A simple trick solves this issue and this is also described on Github. However, some users also get This update only applies to machines with the Windows Subsystem for Linux, This action is only valid for products that are currently installed, and other.

Here is how to Fix WSL 2 Error 0x1bc set default version 2 in Windows 10 –

  1. Press Win+R, type Appwiz.cpl, and click OK.
  2. Once the Programs and Features appears, locate VM (or VM VirtualBox) and Windows Subsystem for Linux.
  3. Right click on each of them and select Uninstall. Follow the on-screen guidelines until the completion of removal.
  4. Reboot your computer.
  5. Update to the Windows 10 2004 using Cumulative Update Preview for Windows 10 2004 KB4568831. You can follow Windows 10 Build 19042.421 Beta Channel 20H2 KB4568831.
  6. Now, right click on wsl_update_x64.msi kernel file and select “Uninstall”
  7. Install the Windows Subsystem for Linux and VM. You can get help from How to Install Linux Subsystem on Windows 10.
  8. Again restart your system.
  9. Install wsl_update_x64.msi kernel (See – https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel).
  10. Finally, open command prompt as administrator.
  11. Type the command line wsl --set-default-version 2 and press Enter.
  12. WSL 2 Error 0x1bc will be fixed hopefully.

That’s all!!!

Repair any Windows problems such as Blue/Black Screen, DLL, Exe, application, Regisrty error and quickly recover system from issues using Reimage.

   


Go to Windows10


Error: 0x1bc when wsl —set-default-version 2

I installed Ubuntu 20.04 after reinstalling a fresh install of Windows 10 after formatting. When I run the following command, I notice Ubuntu is using Version 1.

PS C:Windowssystem32> wsl --list --verbose
  NAME            STATE           VERSION
* Ubuntu-20.04    Running         1

When I try to set default version to 2, I get an error.

PS C:Windowssystem32> wsl --set-default-version 2
Error: 0x1bc
For information on key differences with WSL 2 please visit https://aka.ms/wsl2

when I try to add a apt-key in Ubuntu I get issues. Not sure if related.

$ curl https://baltocdn.com/helm/signing.asc | sudo apt-key add -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1700  100  1700    0     0  26153      0 --:--:-- --:--:-- --:--:-- 26153
gpg: can't connect to the agent: IPC connect call failed

What should I do?

Archived post. New comments cannot be posted and votes cannot be cast.

Понравилась статья? Поделить с друзьями:
  • Wow ошибка при скачивании
  • Wsnt70 dll ошибка
  • Wsaewouldblock resource temporarily unavailable sap ошибка
  • Wusa ошибка 2359302
  • Wsman enumeration возникла ошибка код ошибки 2150858770