Compatibility with Offline-Optimizer?

pmikep

Active Member
I'm gonna guess that the answer to this is "No." (Haven't tried it yet, so could answer the question myself I suppose.)

But since Clanger has been pushing me to make an image of my OS and work on it, I have been doing a bunch of research today. I tripped across Offline-Optimizer. (Mentioned here in the forum one time.)

While it appears that both O-O and NTLite do much of the same thing (although not live for the former), it appears that one advantage of O-O is that they have the de-bloating and de-servicing scripts already in place.

So, naturally, since two heads are better than one, I was wondering if it's possible to run a fresh iso thru O-O, just to de-bloate and de-service it, and then run that through NTLite for the usual stuff?

I suppose an option would be for nuhi to offer de-bloat and de-service (a la Black Viper) scripts. But 1) I don't expect that he wants to get into that business (with all the support calls) and 2) others here have already offered those. (It's just a matter of sorting through them all and trying to find the "best.")
 
de-servicing scripts

What do you mean by that?

I don't see any advantage in using Offline-Optimize if you can use NTLite with all its features. The only advantage may be with the components returning when installing cumulative updates in case you only remove the system apps using the Offline-Optimize script and Windows Apps with any tool but do not remove other components. Even this advantage will be limited as I have already read reports of components returning in 20H2 even using the Offline-Optimize script.
 
You're correct that there's no advantage. I tried Offine-Optimize later. First, it didn't work for me, in that it didn't make a bootable iso. But perhaps I did something wrong. But second, it's not user friendly like NTLite in that it doesn't tell you what the consequences of removing this or that is.
 
i wouldnt use OffOpt asis on a main install. run it on a test install, see what problems it gives me then pull it apart and cherry pick.
 
Yeah, tried it in a VM. Wouldn't boot. Gave up. I could harvest the Reg hacks if I wanted. But there were so few and so uncommented that I didn't bother.
 
You're correct that there's no advantage. I tried Offine-Optimize later. First, it didn't work for me, in that it didn't make a bootable iso. But perhaps I did something wrong. But second, it's not user friendly like NTLite in that it doesn't tell you what the consequences of removing this or that is.
Yes, this is not friendly at all. It complicates things that could be simpler. I've seen reports of other people who can't boot. It changes some uefi-related boot files if I'm not mistaken so maybe that's why it causes problems.

In addition to the complexity in using and reading the PowerShell module and its smaller scripts there are several unnecessary or very personal tweaks. For example it deactivates the autorun and if you don't read the script you will only know it after installing the image. There are other security-related tweaks that are overkill and possibly will reduce performance.
 
Clanger it was a long time ago that I looked at the script when it was just a powershell script and not a module so much simpler than it is today so I don't remember, I would have to look again. But I remember some tweaks increasing the amount of bits to something related to .NET cryptography that I personally think is unnecessary but I don't know if it really affects performance. When in doubt I prefer to leave the default.
 
I took a look now. I confess that at the time I deduced by name what the tweak does and did not research thoroughly.

Set-RegistryProperties.ps1
Code:
$RegistryData.EnableStrongCrypto | Out-File -FilePath $RegistryLog -Encoding UTF8 -Append -Force
RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -Type DWord
RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319" -Name "SchUseStrongCrypto" -Value 1 -Type DWord

SchUseStrongCrypto

A value of 1 causes your app to use strong cryptography. The strong cryptography uses more secure network protocols (TLS 1.2, TLS 1.1, and TLS 1.0) and blocks protocols that are not secure. A value of 0 disables strong cryptography. For more information, see The SCH_USE_STRONG_CRYPTO flag.

If your app targets .NET Framework 4.6 or later versions, this key defaults to a value of 1. That's a secure default that we recommend. If your app targets .NET Framework 4.5.2 or earlier versions, the key defaults to 0. In that case, you should explicitly set its value to 1.

This key should only have a value of 0 if you need to connect to legacy services that don't support strong cryptography and can't be upgraded.


This disables Autoplay and Autorun (personal preference):
Code:
$RegistryData.DisableAutoplayAutorun | Out-File -FilePath $RegistryLog -Encoding UTF8 -Append -Force
RegKey -Path "HKLM:\WIM_HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\AutoplayHandlers" -Name "DisableAutoplay" -Value 1 -Type DWord
RegKey -Path "HKLM:\WIM_HKLM_SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer" -Name "NoDriveTypeAutoRun" -Value 255 -Type DWord

This disables notifications and affects Autoplay (personal preference):
Code:
$RegistryData.DisableNotifications | Out-File -FilePath $RegistryLog -Encoding UTF8 -Append -Force
RegKey -Path "HKLM:\WIM_HKCU\Software\Policies\Microsoft\Windows\CurrentVersion\PushNotifications" -Name "NoToastApplicationNotification" -Value 1 -Type DWord
RegKey -Path "HKLM:\WIM_HKCU\Software\Policies\Microsoft\Windows\CurrentVersion\PushNotifications" -Name "NoToastApplicationNotificationOnLockScreen" -Value 1 -Type DWord
RegKey -Path "HKLM:\WIM_HKCU\Software\Microsoft\Windows\CurrentVersion\Notifications\Settings" -Name "NOC_GLOBAL_SETTING_ALLOW_TOASTS_ABOVE_LOCK" -Value 0 -Type DWord
RegKey -Path "HKLM:\WIM_HKCU\Software\Microsoft\Windows\CurrentVersion\Notifications\Settings" -Name "NOC_GLOBAL_SETTING_ALLOW_CRITICAL_TOASTS_ABOVE_LOCK" -Value 0 -Type DWord

There are other tweaks that are also personal preference but I will not detail them all.
 
Back
Top