Windows Sandbox failed to initialize. Error 0x80004001. Not implemented

Question

Windows Sandbox failed to initialize. Error 0x80004001. Not implemented

Darskiy 1

Anonymous

2021-04-28T09:51:04.333+00:00

This is a quick note to let you know that I am currently performing research on this issue and will get back to you as soon as possible. I appreciate your patience.
If you have any updates during this process, please feel free to let me know.

2 answers

Your answer

Anonymous

2021-04-28T09:51:04.333+00:00

This is a quick note to let you know that I am currently performing research on this issue and will get back to you as soon as possible. I appreciate your patience.
If you have any updates during this process, please feel free to let me know.

Answer 1

Anonymous

Hello @Darskiy

First make sure your system meet with all the perquisite list in this article
- Windows 10 Pro, Enterprise or Education build 18305 or later (Windows Sandbox is currently not supported on Home SKUs)
- AMD64 architecture
- Virtualization capabilities enabled in BIOS
- At least 4 GB of RAM (8 GB recommended)
- At least 1 GB of free disk space (SSD recommended)
- At least two CPU cores (four cores with hyperthreading recommended)
2.Try enable Sandbox using PowerShell, open PowerShell as Administrator and run Enable-WindowsOptionalFeature -FeatureName "Containers-DisposableClientVM" -All -Online; 3.Check Windows Updates in your computer and see if there are any pending Windows Updates you have to install;

I would also suggest post this thread on Microsoft Community , users there are more familiar with this issue and are better at solving it.

Or send File bugs and suggestions at Windows Sandbox's Feedback Hub.

Best Regards
Karlie

If the Answer is helpful, please click "Accept Answer" and upvote it.

Darskiy 1 Reputation point

2021-04-29T17:27:10.767+00:00
Sure

Did not help

Sure

Well, initially I published a thread on the answers.microsoft.com, But I was advised to go here ("in the Technet Forum, which is aimed at IT professionals and certainly someone in that community will be able to help you with your question")
Anonymous

2021-05-06T01:31:49.403+00:00

sorry my answer didn't help,

Since there are no clues we suggest that you could contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.

Global Customer Service phone numbers
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
Bruno Araujo 0 Reputation points

2023-02-11T17:02:52.5566667+00:00

This bug has been reported for a year now. Lots of reports.

Still hasn't been fixed.

It's clearly a bug that happens because of upgrading from Windows Home to Pro and a dependency present in the Pro version not being automatically installed on systems that upgrade to the Pro version.

When users with this issue reinstall Windows it fixes it. Reinstall the home version and upgrade again to Pro, broke again.

Come on now...

Answer 2

Reza-Ameri 45,851 Volunteer Moderator

Make sure you are running all updates.
Send a feedback through the Feedback Hub app.
In case you have VMware or other virtualization technology, uninstall it and restart your PC (just for test).
Make sure you have enabled the virtualization technology in your UEFI/BIOS.

Darskiy 1 Reputation point

2021-04-28T21:27:33.757+00:00

OS Build 21337.1010.
VMware or similar software is not installed.
Virtualization technology ofc enabled.
Reza-Ameri 45,851 Reputation points Volunteer Moderator

2021-04-29T13:20:42.767+00:00

Try open start and search for feedback and open the Feedback Hub app and report this issue.