Windows 10: This installation package could not be opened in Sandbox

Discus and support This installation package could not be opened in Sandbox in AntiVirus, Firewalls and System Security to solve the problem; I was really looking forward to using Windows Sandbox for testing the installers I generate as result of my build. Unfortunately, right off the bat... Discussion in 'AntiVirus, Firewalls and System Security' started by DorCyber, Nov 1, 2019.

  1. DorCyber Win User

    This installation package could not be opened in Sandbox


    I was really looking forward to using Windows Sandbox for testing the installers I generate as result of my build.

    Unfortunately, right off the bat ran into the "This installation package could not be opened …" error message. Have tried all of the options related to msi installer service, and none of them worked.

    It is not clear if "new user administrator" works in the sandbox either, since there is not way to sign out and sign back in.

    It would be nice to have a better user guide or online help that explains in more details what are the core requirements for actual testing of "programs" inside the Sandbox.

    For example, it would also be nice to know why, when running an installation of, say, Visual Studio Redistributable C++ Package, one gets the "no memory resources available..." message even though it seems that the package gets installed. At least it shows up under the Programs and Features.


    To summarize, could someone provide a check list of core services, configuration settings required to test installation packages (.msi) inside the Sandbox.

    It would also be nice to get a better idea of what are the permissions/privileges of the WDAGUtilityAccount and can they be elevated.

    :)
     
    DorCyber, Nov 1, 2019
    #1

  2. Windows Installer Error: This installation package cannot be opened.

    Hi AJ,

    Thank you for posting in Community.

    We are glad to provide the assistance required to help you answer your query.

    The above error can occur if the locally cached Windows Installer package (*.msi) file is damaged or corrupted.

    To rectify the above, I suggest that you try the steps mentioned below and check if you are able to install the software successfully.

    • Open the \Windows\Installer folder on your computer's hard disk.
    • Right-click any file with an .msi extension.
    • Click Properties on the shortcut menu. The
      Subject
      box on the Summary tab contains the name of the product that installed the .msi file.
    • Repeat steps 2 and 3 for each .msi file in the \Installer folder, and delete the .msi file for the software that you are trying to install.

    Hope this helps
     
    Vanessa Sohtun, Nov 1, 2019
    #2
  3. 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, Nov 1, 2019
    #3
  4. This installation package could not be opened in Sandbox

    error ox800706d9 sandbox not work

    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

    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, Nov 1, 2019
    #4
Thema:

This installation package could not be opened in Sandbox

Loading...
  1. This installation package could not be opened in Sandbox - Similar Threads - installation package opened

  2. Package Could Not be Registered

    in Microsoft Windows 10 Store
    Package Could Not be Registered: My Microsoft Store package is saying that it could not be registered and I need it to update my apps. Please reply as soon as possible.Thanks Aarav. https://answers.microsoft.com/en-us/windows/forum/all/package-could-not-be-registered/82119902-2df2-4273-a35f-3f66c57f1e60
  3. Windows Security cant be opened and showed "package could not be registered"

    in Windows 10 BSOD Crashes and Debugging
    Windows Security cant be opened and showed "package could not be registered": I just bought a new Zenbook flip 15 with windows 10 home preinstalled and while trying to customize my settings, i realized i cant opened the Windows security and showed "package could not be registered". this is a huge bummer since window security is a provided "Anti-virus"...
  4. This installation package could not be opened.Verify that the package exists and that you...

    in Windows 10 Installation and Upgrade
    This installation package could not be opened.Verify that the package exists and that you...: when i try to use the command msiexec /i this massage This installation package could not be opened.Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. i tried this Step...
  5. This installation package could not be opened.Verify that the package exists and that you...

    in Windows 10 Installation and Upgrade
    This installation package could not be opened.Verify that the package exists and that you...: Hello! I've tried downloading Elgato Game Capture but it keeps giving me " This installation package could not be opened.Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."...
  6. Package could not be registered

    in Windows 10 Network and Sharing
    Package could not be registered: Package could not be registered error when trying to open any office product. I have run sfc scan, dism, reset the photo app even though my photos are actually opening, and did a system restore. Its still giving me the same error....
  7. Package could not be registered

    in Windows 10 News
    Package could not be registered: [ATTACH] [ATTACH]The Microsoft Photos app for Windows 10 is one of the best applications that are available on the Windows 10 operating system. But it may throw up errors at times. One such error is the one that says, Package could [...] This post Package could not be...
  8. "This installation package could not be opened." error message

    in Windows 10 Network and Sharing
    "This installation package could not be opened." error message: I am trying to install TI-Nspire CX Student Software, but everytime I go to run the installer, an error message pops up that reads, "This installation package could not be opened." I contacted Microsoft support because this has happened numerous times to other software, and I...
  9. Error: this installation package could not be opened. verify that the package exists and...

    in Windows 10 Customization
    Error: this installation package could not be opened. verify that the package exists and...: Hi, While installing Java & MySQL and some other apps in windows 10, I am frequently getting this error: Error: this installation package could not be opened. verify that the package exists and that you can access it, or contact the application vendor to verify that it is a...
  10. Installing Dell Drivers: installation package could not be opened

    in Windows 10 Drivers and Hardware
    Installing Dell Drivers: installation package could not be opened: Further to my thread regarding removing the crapware on my new Dell: https://www.tenforums.com/installatio...-crapware.html I've done a clean install, and want to install some drivers from the Dell web site. I've downloaded the files, but if I try to extract or install...