search

OSDeploy / OSDBuilder

PowerShell Module
http://osdbuilder.com
MIT License
193 stars 55 forks source link

OSDBuilder 21.12.15.1 | OSD 22.1.11.2 - SetPath Error #72

Open makeitcloudy opened 2 years ago

makeitcloudy commented 2 years ago

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.

PS C:\Windows\system32> Import-OSMedia
========================================================================================
Import-OSMedia BEGIN
2022-01-12-131126 Get-OSDBuilder: Validating OSDBuilder Content
2022-01-12-131126 WARNING: This version of OSDBuilder only supports:
2022-01-12-131126 WARNING: Windows 10 1607 - 21H2
2022-01-12-131126 WARNING: Windows 11 21H2
2022-01-12-131126 WARNING: Windows Server 2016 1607 - Windows Server 2022 21H1
========================================================================================
2022-01-12-131126 Media: Scan E:\Sources\install.wim
ImageIndex 1: Windows Server 2016 Standard Evaluation
ImageIndex 2: Windows Server 2016 Standard Evaluation (Desktop Experience)
ImageIndex 3: Windows Server 2016 Datacenter Evaluation
ImageIndex 4: Windows Server 2016 Datacenter Evaluation (Desktop Experience)
========================================================================================
Import-OSMedia PROCESS
2022-01-12-131137 Mount Install.wim: O:\OSDBuilder\SeguraOSD\Mount\os131137
                  Image: E:\Sources\install.wim
                  Index: 3
                  Mount Directory: O:\OSDBuilder\SeguraOSD\Mount\os131137
Mount-WindowsImage : The request is not supported.
At C:\Program Files\WindowsPowerShell\Modules\OSDBuilder\21.12.15.1\Private\AllFunctions.ps1:4744 char:9
+         Mount-WindowsImage -ImagePath $SourceImagePath -Index $Source ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Mount-WindowsImage], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.MountWindowsImageCommand

WARNING: Unable to locate RegHive at O:\OSDBuilder\SeguraOSD\Mount\os131137\Windows\System32\Config\SOFTWARE
OSDeploy commented 2 years ago

Is O:\OSDBuilder on a Local or Network path? Dism will only mount to a Local Drive

makeitcloudy commented 2 years ago

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 !