@ashish1989, "Packages" relates to Features on Demand (FOD) packages... ... they are available (dormant) packages - should you wish to employ them... removing them, saves you (maybe) a few megabytes (on a completed [modified] image) - not worth it The disadvantage is (once removed) you have to go through a far more incovenient method to re-integrate/re-install them... Should you (have the need, or) wish to. ... best left alone, unless you (actually) know what you are doing (... and I am sorry if you find this offensive.. but you don't) so... set your packages parameter to "None" you can take my advice or not, up to you........................... Already (including other contributions) posted info on how to deal with this script, but so far, can se no evidence that you are paying attention ... and seriously if you can't follow this, .... if I make a comment here... I will probably be banned S******
Negative, I was able to manually delete the folder without needing to unmount anything or reboot, etc.
FWIW, I killed all instances of explorer.exe (like I often have to do with W10UI) and it still left the Temp folder. Edit: The frown was just some added flair. Fortunately, the folder deletes without having to unmount anything, reboot, etc as I previously noted.
The Offline_temp bug seems to be happening with ISO sourcefile. Seems like the ISO folder inside the temp directory is not being deleted as powershell.exe process binds itself on the files and locks them. Am trying to find an alternative way how to copy the ISO files into the directory. Maybe this fails even in the original script as i haven't touched that code at all. EDIT: Seems like in powershell 7 is not happening, so for now, if you want ISO remastering use powershell 7.
I'm going to do a Windows 11 guide in OP soon. After much testing, I figured out you can't remove any Packages in Windows 11 I don't think. So I just keep it at "None" Edit: And I'm going to include .zip files of premade lists with the most common working apps removal as well. What will work for most people.
With my testing agree you can easily break both Win10 & 11 with too much "Package" removal, I like you select "None".
Windows 10 I just do a "Blacklist" below. It breaks the script Windows 11 though. Code: { "PackageName": [ "Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.22000.1", "Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.22000.1", "Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.22000.1", ] }