Script Issues (False Positives)

[Lucero7919]

Hi there, it appears that there are quite a few issues with this script. When wrapping it into a PoSH transcript log, it's full of errors when trying to remove the AppxPackages, but like I say, they "appear" to be removed. Is there a full way to test this script in a WinPE environment, without continually having to start the Windows install unattend?

Examples of errors:

TerminatingError(Remove-AppxProvisionedPackage): "The system cannot find the path specified. FullyQualifiedErrorId : Microsot.Dism.Commands.RemoveAppxProvisionedPackageCommand Remove-AppxProvisionedPackage : The system cannot find the path specified.

[d3adconnection]

Hello, these errors are probably because not all of the AppxPackages I define in the script are present on the system. The list includes names of packages that were bundled from earlier versions of Windows 10. I didn't include a check if the AppxPackage exists because it does not have any negative effects, but it will produce error messages in the script's output (whether to a log or the console) I'll do a once over later and see if I can clean up the output from the script for better logging purposes. Thanks!

[Lucero7919]

No worries, thanks for checking. There are a few others, which would be a joy to have working, like WinGet. Import-Module ; The specified module 'Microsoft.WinGet.Client was not loaded because no valid module file was found.

Running here as SYSTEM would alleviate a whole host of problems of trying to script WinGet to update, run on first logon (as User).

One other thing I am trying to work on is running local apps during WinPE (like Office CTR.exe). It appears that there's a UAC prompt hiding somewhere that can't be interacted with, which is annoying, but probably not insurmountable.

I've been toying with the idea of making your script run in PoSH 7 by injecting PoSH 7 into the Win11 boot WIM. That would enhance the number of available cmdlets in WinPE.

Keep up the great work.