Hey @MSMG I assume there's no problem then with those (other) nr's on some folder/files? And thx in advance for verifying once more. Seems your busy....so take your time And keep up the great work with all those updates!
Your pack files appears to be free from folder permission bugs, only difference is those d:X XXX do changes, don't know if it changes for different installation. I have checked with my packs and the original Windows installation WIM's they do have the same d:X XXX. Do advise you to use a VM for creating packs so that the originality won't get change.
hmm I often wonder how a simple Windows 10 user should feel when it comes to SSU's and LCU's I think this philosophy of M$FT is purposely made for these users not to try to modify anything within the operating system is just remember the UAC; but thank heavens that I am not part of this group and change even what is necessary, I remove the useless s**t and add many useful things that ironically come from the Git hub that happen to be owned by M$FT itself ...
Hello. Is 19043.867 considered as a release candidate? Because all I can find is that it was pushed to the beta channel. edit: nvm as bleeping gave me the answer I was looking for,
how can I remove onedrive using a script that shows hidden packages in the image? I need to do this completely automatically
Hi Hm, actually I'm having problems to get key-strokes being accepted in the Remove-Panel. I'm typing 'A' ( for Example ), but this Letter vanishes as soon as I let go the key and nothing happens. 'X' for ' back ' is being accepted. I tried to change the Rights of the Folders, but vain. Thanks for a Hint in Advance
May be its the spaces in the font filename creating issues, do try removing the spaces in the filename.
Just copy all the updates to <WHD\w10\x64\10.0.19041> and use the menu Integrate Updates->Integrate WHD Updates Menu-Integrate to Windows Installation Image.
OneDrive Package names Microsoft-Windows-OneDrive-Setup-Package Microsoft-Windows-OneDrive-Setup-WOW64-Package
When you press A to select all components the + sign prefixed to component name will change to - sign, this means all components are selected. Now go to previous menu (3->1>2 - Start Removing Windows Components) to start removing the components.
I have checked with fonts that have no spaces in their names with the same error. As far as I can see the path variable referred to in the error is the copy path that the fonts are copied from? Indeed Code: $fPath = "$($folder.getDetailsOf($obFont, 194))" is empty Someone more knowledgeable than myself on powershell scripts may know what is going on? Anyway it's not essential for me right now. Thanks for your help.
Will I need to mount registry keys to remove packages? Do I need to use your script to show hidden packages in this case?