Open makeitcloudy opened 2 years ago
Is O:\OSDBuilder on a Local or Network path? Dism will only mount to a Local Drive
Hi ! thank you for your reply The O drive, was just another drive brought into the virtual machine which was windows 10 19H2 or 21H2 - can not recall at the moment (can check if this is needed). Then when it failed I thought that will map this extra drive as a folder on the operating system level, which did the trick, so the path remains the same, but on the OS level the C:\OSDBuilder is a pointer towards this extra drive - and this way it works like a charm. Never the less the -setPath dropped that error message attached above. It's not a show stopper, but definitelly something to consider with the next release. Btw thank you for all the effort you put into this solution - highly appreciate it !
there seems to be an issue with Import-OSMedia when the OSBuilder -SetHome is specified to something different than the default location which goes hands in hand with the installation of the module and it's default settings.
for windows 2016 1607 default iso downloaded from the public channel there is following error message during the Import-OSMedia execution.