Windows 10: Windows 10 Sandbox computer name too long, other issues

Discus and support Windows 10 Sandbox computer name too long, other issues in Windows 10 Ask Insider to solve the problem; I work with application packaging (SCCM, PSADT, etc) and am looking into using the Sandbox feature to further automate the testing of our packages.... Discussion in 'Windows 10 Ask Insider' started by /u/khaffner91, Dec 9, 2019.

  1. Windows 10 Sandbox computer name too long, other issues


    I work with application packaging (SCCM, PSADT, etc) and am looking into using the Sandbox feature to further automate the testing of our packages. I've looked into the .wsb-files for configuring the Sandbox, tested a few hours and stumbled upon a few problems.

    1. The hostname is a guid. This becomes an issue when dealing with the computer name as the max length is 15 characters. I noticed it when I tried to launch psexec -isd cmd.exe to get a command prompt as the system account. psexec can't find the local computer, I believe this is due to the long computer name. Renaming the computer does not work, as it requires a restart to apply, which destroys the sandbox.
    2. ^How can I launch a process as system?
    3. The user that automatically logs on is named WDAGUtilityAccount. The description is "A user account managed and used by the system for Windows Defender Application Guard scenarios.". Why this account? The local Administrator account seems a better fit.
    4. There are missing powershell modules, for example the PackageManagement module. I resolved this by mapping the host PackageManagement module folder and using a logonscript in the .wsb file to copy it to the sandboxed powershell module folder. Any better solution will be appreciated.
    5. MappedFolder can't take a relative path, and can only mount to the desktop of the logged on user. Bigger flexibility would be nice.
    6. Only one LogonCommand. Not even possible to string together multiple commands with &&. Am I doing it wrong? Mounting a script and calling that is possible, but multiple LogonCommand entries in the .wsb file should be an option.
    7. Custom Sandbox images would be cool. I'd love to spin up a sandbox with the needed vcredists, .Net framework and other dependencies for the apps we're testing.
    8. My host is 1909. The sandbox is 1903. I thought the sandbox was supposed to be based on the host version.

    I think what I really want is for Sandbox to behave more like docker Windows 10 Sandbox computer name too long, other issues :) Hyper-V with checkpoints are also an alternative, but I like the ephemerality of the sandboxes.

    submitted by /u/khaffner91
    [link] [comments]

    :)
     
    /u/khaffner91, Dec 9, 2019
    #1
  2. Naresh_K Win User

    Microsoft sandbox stoped working

    Hi,



    Thank you for writing to Microsoft Community Forums.



    Please be informed that our developer team is aware of the issues with Sandbox and is working on resolving it. We do not have an ETA as of now, however I encourage you to send a feedback to our developer team via
    Feedback hub. As a suggestion you can try disabling and enabling
    the sandbox to check if that works. Please follow the steps mentioned below:



    1. Open Control Panel.
    2. Then click on all Control Panel Items.
    3. Then click on Programs and features.
    4. Then on the left hand side, click on Turn Windows features on or off.
    5. Then uncheck the option: Windows Sandbox.
    6. Then restart your computer.
    7. After restart, please enable it and check if the sandbox is working.


    Also make sure that you meet all the requirements for Windows Sandbox.
    Your patience and understanding will be appreciated in this matter.



    Regards
     
    Naresh_K, Dec 9, 2019
    #2
  3. Fix for Sandbox

    Microsoft has acknowledged this issue now:

    Windows Sandbox may fail to start with error code “0x80070002”Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.


    Affected platforms:
    • Client: Windows 10, version 1903

    Next steps: We are working on a resolution and estimate a solution will be available in late June.
     
    hsehestedt, Dec 9, 2019
    #3
  4. Windows 10 Sandbox computer name too long, other issues

    Windows Sandbox not enble

    Windows Sandbox not enble

    Windows Sandbox not appear in the start menu. I tried to enable it from "Turn Windows features on or off" but the Windows Sandbox appears in grey there and when I roll over it the message "Virtualization support is disabled in firmware" pop up. Please help
    on this issue.

    before installing Windows sandbox check to see if virtualization is enable by right clicking over taskbar and going to task manager then click the performance tab go down to Logical Processors under that is Virtualization which should say enabled,

    if not enabled virtualization in the bios refer to your computer guide for motherboard make and model,

    If Virtualization is enabled in the bios then you have issue with Windows 10 services under Administrative Tools.

    follow this below should get you going.

    For Windows 10 1903 sandbox wont start errors all you do is just restart the following service under Administrative tools



    Container Manager Services.



    then reopen sandbox should start up like normal.

    If it does not start up do the following below.



    If you have Hyper-V installed and Virtual disk is turned on under Administrative tools you must restart all these services



    1. Container Manager Services
    2. HV Host
    3. Virtual Disk
    4. Hyper-V Virtual Machine Manager
    5. Hyper-V Host Compute Service
    6. Network Virtualization Service

    Do this in the following order

    1. Right click over (Network Virtualization Service) click restart and wait.
    2. Right click over (Virtual Disk) click restart and wait.
    3. Right click over (Hyper-V Virtual Machine Manager) click restart and wait
    4. Right click over (Hyper-V Host Compute Service) click restart and wait
    5. Right click over (Container Manager Services) click restart and wait



    Check these services are still on

    Application Guard Container Service (If installed)

    Remote Procedure Call (RDC) (""This must be running as most of the others rely upon its function it should never be disabled"")



    Once they are checked start sandbox and it should open up if it does restart your computer to ensure the services are still functional are a restart of computer this should also be done if sandbox does not start up once these services are restarted
    and checked.



    Created By Eric O'Malley

    17th June 2019

    follow this guide if the sandbox program wont start or failures to open.

    Windows Sandbox failed to start

    A Work Around

    To get

    Windows Sandbox

    Working again

    Created

    By

    Eric O’Malley

    10/06/2019





    Well I work out a solution to get Windows Sandbox going again it’s not the best solution but work around follow the steps below and hope it works for all of you guys.



    1. The first thing you have to do is turn off Windows Defender Random Folder Protection
      or the anti virus random folder protection.
    2. Next turn off Windows defenders Tamper protection Or the Anti-Virus Tamper protection
    3. Once that turn off Go to Control Panel open it
    4. Location Administrative Tools
    5. Next head to Services and open that
    6. Scroll down to Container Manager Services
    7. Turn off Container Manager Service only
    8. Leave service screen open but minimize it
    9. Next go to control panel location and open File Explorer Options
    10. In File Explorer Options Untick the following:



      • Don’t Show Hidden Files, Folders, or Drivers
      • Hide Empty Drivers
      • Hide Extensions Known Files Types
      • Hide Merge Conflicts
      • Hide Protected Operating Systems Files



    1. Now move File Explorer Options to one side of your screen
    2. Go back to Control Panel
    3. Locate and open Program and Features
    4. Go to Turn Windows Features on or Off
      open it

    5. Scroll down to Windows Sandbox
    6. Untick Windows Sandbox
    7. Click ok to uninstall Windows Sandbox
    8. Close off only the screen that removed Windows sandbox
    9. Next go to your main drive usually C: Drive
    10. Location ProgramData
      • We need to get to this location (C:\programData\Microsoft\Windows\Containters\Sandboxes)



    1. Even open it or expand ProgramData
    2. Locate Microsoft open it or expand
    3. Scroll down to Windows open it or expand
    4. Now go to the folder called Containers
      open it or expand
    5. Now you should see Sandboxes
      • You Should be at this location Now

    (C:\programData\Microsoft\Windows\Containters\Sandboxes)



    1. Now in that folder Sandbox is folder that looks like this



      • 4040f074-2ff6-471c-9f38-4836db85fff6
      • Inside it is sandbox.vhdx



    1. What we need do is delete all the strange folders keys that’s in

    (C:\programData\Microsoft\Windows\Containters\Sandboxes)



    1. If it does not delete just wait a few seconds and try again



    Caution do not delete the folders from recycle bin yet



    1. Next go to the folder below it called
      Zygotes




    (C:\programData\Microsoft\Windows\Containters\Zygotes)



    Repeat the steps you did at Sandboxes and delete the strange folder keys with its contents but do not delete what’s in recycle bin.



    1. Repeat the step you did at Sandboxes and delete the
      strange folder key with its contents

    2. If it does not delete just wait a few seconds and try again
    3. Now move the open explorer screen to one side of the screen
    4. Head back to control panel
    5. Locate and open Program and Features
    6. Go to Turn Windows Features on or Off
      open it

    7. Scroll down to Windows Sandbox
    8. This time re-tick Windows Sandbox and close and allow it to reinstall the sandbox
    9. Close only the install screen
    10. Go back to services and Restart Container Manager Service
    11. Leave Services screen open move it to once side again.
    12. We now head to Start then Settings
    13. Scroll until you find Windows
      Sandbox click it twice.
    14. Wait and see how the screen opens if it give you another error
      repeat this process
    15. When you open Windows Sandbox it should
      hang for 5 to 10 minutes without any error message
    16. What it’s doing is rebuilding its image then it opens back to what it was in default settings.
    17. Once you have sandbox reopened and its got the icons load close it pressing the
      red X
    18. Then reopen Windows Sandbox to see if it opens up again.
    19. If it does you fixed it.
    20. Now we can turn back on
      • Windows Defender Random Folder Protection
        or the anti virus random folder protection



      • Windows defenders Tamper protection Or the Anti-Virus Tamper protection



    1. Retest Windows sandbox will open again with the above
      turned on
    2. If it does the next thing is to restart your computer and
      Repeat the opening of Windows sandbox.
    3. Once all is well your right to continue
    4. You can delete the folders in your recycle bin too.



    Created by

    Eric O’Malley

    10/06/2019
     
    viennafiji, Dec 9, 2019
    #4
Thema:

Windows 10 Sandbox computer name too long, other issues

Loading...
  1. Windows 10 Sandbox computer name too long, other issues - Similar Threads - Sandbox computer name

  2. File name too long

    in Windows 10 Gaming
    File name too long: I still have an issue with the error "the file name is too long", although it is not. Ihave changed the value in the longpathsenable Keyloccalmachine using registry editor, restarted and same issue !Please advise !...
  3. File name too long

    in Windows 10 Software and Apps
    File name too long: I still have an issue with the error "the file name is too long", although it is not. Ihave changed the value in the longpathsenable Keyloccalmachine using registry editor, restarted and same issue !Please advise !...
  4. File name too long for destination folder

    in Windows 10 Software and Apps
    File name too long for destination folder: I have a parent folder containing multiple subfolders 100+ within. Every folder name is well under 256 characters. I need to transfer this particular parent folder regularly between my computer drives and have had no issue initially. However out of the blue I start receiving...
  5. File name too long for destination folder

    in Windows 10 Network and Sharing
    File name too long for destination folder: I have a parent folder containing multiple subfolders 100+ within. Every folder name is well under 256 characters. I need to transfer this particular parent folder regularly between my computer drives and have had no issue initially. However out of the blue I start receiving...
  6. Get-SmbServerConfiguration: The file name is too long

    in Windows 10 Gaming
    Get-SmbServerConfiguration: The file name is too long: Every time in PowerShell I run the Get-SmbServerConfiguration utility I am unable to get any good results as PowerShell puts up a "file name is too long" error. Curiously this doesn't happen when I run Get-SmbServerNetworkInterface, for example, even though that command is...
  7. Get-SmbServerConfiguration: The file name is too long

    in Windows 10 Software and Apps
    Get-SmbServerConfiguration: The file name is too long: Every time in PowerShell I run the Get-SmbServerConfiguration utility I am unable to get any good results as PowerShell puts up a "file name is too long" error. Curiously this doesn't happen when I run Get-SmbServerNetworkInterface, for example, even though that command is...
  8. Delete files with [TOO] long file names .......

    in Windows 10 Customization
    Delete files with [TOO] long file names .......: The only post I could find was one from this forum from AUGUST 23, 2017 WINDOWS 7/64, but not Windows 10. That dealt with my problem: DELETING FILES WITH NAMES TOO LONG.The instructions said to: Hi, Windows uses a naming convention called Long Filenames LFN. The LFN system...
  9. File name too long

    in Windows 10 Support
    File name too long: I run Win10: [img] And a browser save on the HDD disk, with filename counting 255 letters. And I cannot rename it, move it, or delete it. And I have enabled in the group policy Win32 long file names: Enable or Disable Win32 Long Paths in Windows 10 How can I get rid of...
  10. file name too long

    in Windows 10 Network and Sharing
    file name too long: how to resolve this issue in windows 10 https://answers.microsoft.com/en-us/windows/forum/all/file-name-too-long/783521af-d0ec-410b-826e-67a50a90159c"