Windows Sandbox isn't functioning properly?
Windows Sandbox isn't functioning properly?
Update your post with complete hardware details and operating system information. Provide the power supply specifications, including make, model, wattage, age, and condition (original, build, refurbished, used). List the disk drive specifications and current storage usage. Include a detailed inventory of all connected peripherals. Specify whether the network connection is wired or wireless. Add a comprehensive list of installed VPN, security, and virtual machine software. Note any potential compatibility issues.
I had two antiviruses set up once... That was a bit chaotic...
It functioned perfectly before, and since then the hardware stayed the same; I've been using it for seven years without any problems, so that's not related to hardware.
In either case, I listed my VPN and security software. I have Hyper-V and everything worked smoothly; I don't recall exactly when this started, but it might be after the 24H2 update.
Even though the physical parts weren't altered directly, they can still shift or deteriorate over time because of factors like age, temperature, movement, etc.
Electronic parts may weaken or stop working gradually, sometimes with a sudden "snap" and a small amount of smoke.
Seven years is sufficient for components to wear out and cause issues—probably due to many influencing factors. Under the right circumstances, a "perfect storm" can trigger these problems. They can be sporadic and often dismissed as minor glitches.
That trend might worsen if something like an update occurs, which could slightly spark a series of complications.
= = = =
Check the Reliability History or Monitor/Event Viewer.
You should search for error messages, alerts, and any logs recorded just before or when the issue started. Pay special attention to entries involving VM or specific system resources.
For instance, a failing power supply can cause widespread problems. A rise in errors or more varied errors generally points toward power issues.
For this situation, focus on logs tied to Hyper-V, Sandboxing, etc., especially those that appeared or vanished when you removed and reinstalled software.
Yeah, everything else is working fine, I play games just fine, use computer every day, and everything is fine, but a power supply is causing Hyper-V's default switch to not work... Nice attempt, but no.
Like I said, if I'm not mistaken, the issue started to happen soon after installing 24H2 update, which was about a year ago; I was sort of hoping MS would fix it any time soon, but I installed all possible updates and there's still no solution... So no, this is not a hardware issue, it's Microsoft issue.
Either way, I ran dism multiple times, sfc /scannow, all to no success. I even uninstalled both Hyper-V and Sandbox, and reinstalled them, but that didn't solve the issue. Either way, if there's no solution, I'll just blame Microsoft, I see no other way
Considering the message you received, it highlights issues related to system resources and performance. Remember that power supplies offer multiple voltage options (3, 5, and 12) for different components. Any deviation from expected voltages may lead to complications. It's important to note that a single change in settings can significantly impact operations.
For more details, you can refer to the official documentation: https://learn.microsoft.com/en-us/window...v/overview
The key point is optimizing hardware usage. If the hardware isn't functioning properly due to insufficient power or other factors, related applications or virtual machines may also experience problems.
I don’t have a personal stake in this matter. The goal is to investigate further and understand what’s happening. It could be the PSU, or it might involve Microsoft. Neither of us has a clear interest here.
It would be helpful to examine Task Manager, Resource Monitor, and Process Explorer. Use all three tools sequentially, focusing on one at a time. Try to identify differences in behavior when VMs are running versus not running. Observe any changes during issues to pinpoint the exact resource usage and performance variations.
Can I begin the Sandbox using another virtual switch you set up in Hyper-V? I want to verify that it functions properly.
I don't understand the answer yet, but I'm curious about the overall goal. The reason for using a different virtual switch is to maintain flexibility and reliability during testing. It's important to have a backup plan so that if something goes wrong, you can still recover or continue your work smoothly.
My VMs in Hyper-V don't start with the default switch as effectively, but they do start with the one I set up. If I discover a method to launch a Sandbox using another virtual switch, it would mean the protection from being a PSU or other component isn't working. This suggests the issue lies with Microsoft, not me or anyone else. Also, does your Sandbox function properly? Do you have 242H2/25H2? (I think 25H2 is just an update for 24H2 and doesn't bring any new features.)
Cruisetung, are you certain you're in the correct thread? I mentioned I have 24H2, which implies Windows 11 (the latest for Win10 was 22H2), I noted I have Hyper-V, and I didn't say anything about nesting. I might or might not have a nested WinWhichever with a working Sandbox, but that wouldn't provide anything useful since it would be nested—something different from the base OS. Please confirm you're in the right thread and if not, could you delete your last (and only) post here?