I don't no i set it to auto and still don't work it was on manual not sure what the default should be for the internet connection sharing service. i have not seen that hyper-v remote error thing i have let it sit there for 20 min on a blue splash screen with nothing no error .
I know not to play with hyper v services LOL i turned one on by mistake and had a error critical process died and blue screen lol my own dumb fault pocking around lol
-Hyper-V Remote Desktop Virtualization Service
When I set that one to automatic, Sandbox was working.
Also, set these services to auto when the screen was blue:
-AllJoyn Router Service
-Application Layer Gateway Service
-Internet Connection Sharing (ICS)
All of them were disabled. All hyper-V stuff are disabled too + many others.
from MS 8 gig off ram is the recommended
Prerequisites for using the feature
- Windows 10 Pro or Enterprise Insider build 18305 or later
- AMD64 architecture
- Virtualization capabilities enabled in BIOS
- At least 4GB of RAM (8GB recommended)
- At least 1 GB of free disk space (SSD recommended)
- At least 2 CPU cores (4 cores with hyperthreading recommended)
You won't do miracles with your old chipset Tony.
Be my guess!
i have ran plenty of virtual machines have a windows 98 a xp and a windows 7 and 8 hyperv machines , all run perfect my chipset works fine and dandy , only thing not working is a sandbox and i just got a answer from MS tech its a known issue and a fix is coming
Happy ending then!
What is the build number you have? Mine is*113.
build number 18362.116 windows 10 pro
Quote