@KiDFuZioN The Configuration.json (Example) file included with the scripts has all values filled in. The Configuration.json file generated by the script (Found in the Optimize Logs.zip) does not, Most certainly not in my case... as to its validity, will take what you said on board.. Code: { "_Info": [ "This is a JSON based Configuration file for Optimize-Offline.", "Ensure proper formatting is used when editing the JSON parameter values.", "Boolean parameter values use true and false. String parameter values must be enclosed in double-quotes." ], "SourcePath": "D:\\19037.1000\\sources\\install.wim", "WindowsApps": "Whitelist", "SystemApps": true, "Capabilities": true, "Packages": , "Features": true, "DeveloperMode": , "WindowsStore": , "MicrosoftEdge": , "Win32Calc": , "Dedup": , "Registry": true, "Additional": true } RE: Culture Workaround (en-US to en-GB) Script fails when using Powershell 6 - Failed to import the localized data file (Optimize-Offline.psd1) however, works with all other powershell iterations .. have just noticed filename differs in the psm1 script Import-LocalizedData -BindingVariable OptimizedData -FileName Optimize-Offline.strings.psd1
@KiDFuZioN Initial [Root] Code: { "_Info": [ "This is a JSON based Configuration file for Optimize-Offline.", "Ensure proper formatting is used when editing the JSON parameter values.", "Boolean parameter values use true and false. String parameter values must be enclosed in double-quotes." ], "SourcePath": "D:\\19037.1000\\sources\\install.wim", "WindowsApps": "Whitelist", "SystemApps": true, "Capabilities": true, "Packages": false, "Features": true, "DeveloperMode": false, "WindowsStore":false, "MicrosoftEdge": false, "Win32Calc": false, "Registry": true, "Additional": true } Generated [Optimize Log] Code: { "_Info": [ "This is a JSON based Configuration file for Optimize-Offline.", "Ensure proper formatting is used when editing the JSON parameter values.", "Boolean parameter values use true and . String parameter values must be enclosed in double-quotes." ], "SourcePath": "D:\\19037.1000\\sources\\install.wim", "WindowsApps": "Whitelist", "SystemApps": true, "Capabilities": true, "Packages": , "Features": true, "DeveloperMode": , "WindowsStore": , "MicrosoftEdge": , "Win32Calc": , "Registry": true, "Additional": true }
https://forums.mydigitallife.net/th...-1909-and-ltsc-2019.80038/page-5#post-1563151 Don't edit "Start-Optimize.ps1", use only the Configuration.json file and see if the problem persists
Which problem the Invalid JSON primitive: . The missing false references, or that it doesn't run under Powershell 6 will run a test using en-US culture and an en-US image as author intended, but, needless to say to say, I need this to run on an en-GB image, hence all the tinkering. there is also a request on git hub for the script to be made available for other cultures, another reason why I persist.
I changed en-US to en-GB in the PowerShell script for Windows 1909 and everything worked fine. Oh, and the folder name as well.
@GodHand Thanks for this wounderfull script. @drew84 Thanks for showing how to use this sricpt. @KedarWolf Thanks for posting and maintaining the thread. I made the best debloated Windows 10 which is almost perfect with no errors using this script, faster and better than any other software.
NTLite is another way , but every time I talk about it, I feel like I am a part of an advertisement...
Hi guys, do you know if there's any way of deleting the system apps files that are left out in the windows\systemapps folder without having sfc /verifyonly triggering integrity check errors? I've removed the inbox apps registry keys in my offline wim file (following an old post here), but all those folders are left there. I think there is a method to remove all those crappy folders because i can get rid of them withouth any sfc error if i use NTLite, but i'd prefer to use a different method. thanks all in advance.
@GodHand @drew84 I like to try this script on 19035 20H1 OS. May I try or need an update to work with 20H1 OS
Script is officially recommended only up to 1909 (19H2) But you can use at your own risk (as I have done) up to current 19041 ... just needs some minor modifications to psm1 script, as addressed previously. Good Luck... @Kedar Wolf another addition for you (Optimize-OfflineRoot Directory\Src\Public\) Changed the en-US folder to en-GB, <<<--- EDIT 2
Only just noticed this Opimize-Offline 4.0.0.1: Module Disclaimer Support will not be given to users who attempt to optimize unsupported builds or previously modified images. wonder if that statement is also meant to include alternative localised cultures... somewhat disappointing if that is the case