I shrunk "_Info": [], and your configuration file worked. I too got an error after using your file so give that a try. Edit: But specifically, it's the 2nd to last line, "Services : None | Select | List | Advanced", (comma was missing)
According to this user you need to add an additional binary file to the installation. Problem is that this project is meant to be open source, adding that binary would break this rule. I am keeping the code i have added there, it will not hurt anything. Let's see in the future if Microsoft makes things work
Latest release and latest commit. Windows 11 22000.675 IoT Code: Index : 0 Exception : Cannot bind argument to parameter 'Path' because it is an empty string. Category : InvalidData: (:) [Get-Item], ParameterBindingValidationException ErrorID : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.GetItemCommand Target : Command : $SaveDirectory = Get-Item -Path $OutputPath Script : D:\Optimize\Optimize-Offline\Optimize-Offline.psm1 Line : 2705 Column : 39
Post your Configuration.json. But look at your OutputPath as the error message is complaining about it.
I don't think it's that, it finds the ISO I point OO to and runs OO just fine. And the ISO OO makes installed just fine. It must be something else.
So it does everything correctly but you're concerned about this error message? Also, what's Windows 11 22000.675 IoT (Edit: Nevermind) ? Are you populating your Lists or running OO all manually?
@gdeliana I was wondering why Nividia drivers were installed automatically on a clean Windows install. I checked the registry. These keys are there. RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "DontPromptForWindowsUpdate" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "DontSearchWindowsUpdate" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "DriverUpdateWizardWuSearchEnabled" -Type DWord -Value "0" These are not in the registry. RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\Device Metadata" -Name "PreventDeviceMetadataFromNetwork" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "SearchOrderConfig" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "ExcludeWUDriversInQualityUpdate" -Type DWord -Value "1" From SelectiveRegistry.ps1 Code: If($SelectiveRegistry.DisableDriverUpdate) { Log $OptimizeData.SelectiveRegistryDriverUpdate RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\Device Metadata" -Name "PreventDeviceMetadataFromNetwork" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "DontPromptForWindowsUpdate" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "DontSearchWindowsUpdate" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "DriverUpdateWizardWuSearchEnabled" -Type DWord -Value "0" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\DriverSearching" -Name "SearchOrderConfig" -Type DWord -Value "1" RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Name "ExcludeWUDriversInQualityUpdate" -Type DWord -Value "1" Start-Sleep 1 }
I think its Microsoft setup overriding those values, as it is the case with the amoled theme. We need to find a way to prevent the OOBE setup from doing that.
I skip OOBE in my unattend.xml. Actually, in Windows 11 skipping User or Machine OOBE is depreciated and will cause your install to error out. I DO skip everything like Account Creation and Wireless Setup though.
@gdeliana If I choose an output path for the ISO, get no errors. But if there is already an ISO with that name in that output path, it errors out trying to create the ISO. Code: Exception : Cannot create a file when that file already exists. Category : WriteError: (D:\IoTEnterprise_22000.iso:String) [Rename-Item], IOException ErrorID : RenameItemIOError,Microsoft.PowerShell.Commands.RenameItemCommand Target : D:\IoTEnterprise_22000.iso Command : Rename-Item -Path $MovedItem.FullName -NewName $NewFileName Script : D:\Optimize-Offline-master\Optimize-Offline-master\Optimize-Offline.psm1 Line : 2729 Column : 6 Could we make it overwrite the existing ISO by default if using the same ISO name and path?
EnableOLEDTaskbar If ($InstallInfo.Build -le '19044'){ $RegistryData.EnableOLEDTaskbar | Out-File -FilePath $RegistryLog -Encoding UTF8 -Append -Force RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced" -Name "UseOLEDTaskbarTransparency" -Value 1 -Type DWord RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Microsoft\Windows\Dwm" -Name "ForceEffectMode" -Value 1 -Type DWord RegKey -Path "HKLM:\WIM_HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize" -Name "EnableTransparency" -Value 1 -Type DWord } -le '19044' ? 22000 not support？