Repository navigation
Mountpoint of Iso #237
|
After the VM is created, the Windows 11 ISO file is still mounted in the VM. Where can I configure the settings so that this no longer happens? HCS: {"Error":-2147024894,"ErrorMessage":"Das System kann die angegebene Datei nicht finden.","ErrorEvents":[{"Message":"Fehler beim Starten von "VM-Name" (ID des virtuellen Computers 782843DE-1B80-5FB3-A84C-AE6F8324B9F5).","Provider":"51ddfa29-d5c8-4803-be4b-2ecb715570fe","EventId":12030,"Flags":13,"Data":[{"Type":"String","Value":"Win11X"},{"Type":"String","Value":"782843DE-1B80-5FB3-A84C-AE6F8324B9F5"}]},{"Message":""VM-Name" Synthetic Storage (Instanz-ID 57485C38-CE38-51D5-AD3B-A248DB55B991): Fehler "Das System kann die angegebene Datei nicht finden." (0x80070002) beim Einschalten (ID des virtuellen Computers: 782843DE-1B80-5FB3-A84C-AE6F8324B9F5).","Provider":"51ddfa29-d5c8-4803-be4b-2ecb715570fe","EventId":12010,"Flags":5,"Data":[{"Type":"String","Value":"Win11X"},{"Type":"String","Value":"782843DE-1B80-5FB3-A84C-AE6F8324B9F5"},{"Type":"String","Value":"Synthetic Storage"},{"Type":"String","Value":"%%2147942402"},{"Type":"String","Value":"0x80070002"},{"Type":"String","Value":"57485C38-CE38-51D5-AD3B-A248DB55B991"},{"Type":"String","Value":""}]},{"Message":""VM-Name": Die Anlage "Path to File\Windows11.iso (Lun 1)" wurde aufgrund eines Fehlers nicht gefunden: "Das System kann die angegebene Datei nicht finden." (0x80070002) (ID des virtuellen Computers: 782843DE-1B80-5FB3-A84C-AE6F8324B9F5).","Provider":"edacd782-2564-4497-ade6-7199377850f2","EventId":12240,"Flags":5,"Data":[{"Type":"String","Value":"VM-Name"},{"Type":"String","Value":"782843DE-1B80-5FB3-A84C-AE6F8324B9F5"},{"Type":"String","Value":"Path to File\Windows11.iso (Lun 1)"},{"Type":"String","Value":"%%2147942402"},{"Type":"String","Value":"0x80070002"},{"Type":"String","Value":"Hyper-V-Verwaltungsdienst für virtuelle Computer"},{"Type":"String","Value":""}]}],"Attribution":[{"OperationFailure":{"Detail":"Start"}},{"VirtualDeviceFailure":{"Detail":"PowerOnCold","Name":"Synthetic Storage","DeviceId":"d422512d-2bf2-4752-809d-7b82b5fcb1b4","InstanceId":"57485c38-ce38-51d5-ad3b-a248db55b991"}}]} |
Replies: 2 comments 1 reply
|
The Once Windows has finished installing and the VM can boot from its VHDX, shut it down and fully exit AppSandbox (including the tray). Back up I checked the config and mount code, but haven't tested this on a running Hyper-V guest. |
|
Thanks @Stormrider80 for reporting the startup failure, @Muguett-DBY for tracing it to the installer ISO, and @miyatsu for the earlier report about slow restarts. With App Sandbox 0.1.14, you can move or delete the original installer ISO once the VM is fully installed. Existing VMs on Windows hosts can start from their virtual disks with their current guest agents. If you like App Sandbox and want to support it, it would be so awesome if you showed people on Reddit, Twitter, YouTube, or wherever you post how you use App Sandbox to do something cool. Even if you just mention it’s one of the tools in your workflow, that would be super helpful and will bring a lot of awareness to the project! |
The
Lun 1in the error is the Windows installer ISO. In v0.1.13, AppSandbox reads that path from the VM'sImagePathsetting, and only attaches it if the value is nonempty.Once Windows has finished installing and the VM can boot from its VHDX, shut it down and fully exit AppSandbox (including the tray). Back up
%ProgramData%\AppSandbox\vms.cfg, then find that VM by itsName=line and clear just the value on itsImagePath=line. Keep the file's encoding and leaveVhdxPath=as it is. Reopen AppSandbox and check the VM boots before moving the ISO. If you've already moved it, you can put it back while checking that the guest boots from the VHDX.I checked the config and mount code, but haven'…