Win10 20H2 anomalies using NTLite

[banko84]

Hi,

It seems that when I do the whole process. Afterwards in Windows after installing Ccleaner and goin into it's settings, I can not save its settings ini file into the Applications folder.
It say's something about not having permissions.

My Preset file is attached.
The base is original file downloaded with MS Download Tool.
Extracted W10Pro WIM file with Power Shell and just deleted the ESD file in the Source folder.

 

[banko84]

It's possible from Settings/Privacy/View attachment 4201

The first option to Disable and Second from Default Enable gave Me this as a result.

 

[banko84]

Still having Permissions error with Ccleaner.

 

[banko84]

Will try this one now.

First Enabel.
Second Disable.

 

[banko84]

Will try this one now.

First Enabel.
Second Disable.

Results will give you the prior acting of things. Meaning after restarting from an account it logs into the same account without options to choose which one you want.

 

[banko84]

The Ccleaner premissions issue is the result of the Culmulative update that has broken all kinds of stuff.
When using the Culmulative update on 1809 and onwards it f.... up some Premission core functionality!

 

[banko84]

The Ccleaner premissions issue is the result of the Culmulative update that has broken all kinds of stuff.
When using the Culmulative update on 1809 and onwards it f.... up some Premission core functionality!

Does someone have any idea what updates should I leave out of W10 1809 to not have Culmulative Update mess up Windows?
Edit: Does Clanger do you have a kind of mid-way Barebone++ with LAN Wifi Smartcard support version of a preset?

Update: Win10_1809Oct_v2_English_x64.iso 08-06-2019 version of the ISO file has the same issue right out of the Box.

 

[Clanger]

Does someone have any idea what updates should I leave out of W10 1809 to not have Culmulative Update mess up Windows?

all CUs. there aint a month go by that a cu dont screw something up.

here is what i did with 1809. download a set of updates and save them to a folder named according to what build number a cu would update to, for example 17763.1234. the next cu update build number would be 17763.1235, and so on. if i had issues with a build number i could easily roll back to one that didnt give a problem.

 

[banko84]

all CUs. there aint a month go by that a cu dont screw something up.

here is what i did with 1809. download a set of updates and save them to a folder named according to what build number a cu would update to, for example 17763.1234. the next cu update build number would be 17763.1235, and so on. if i had issues with a build number i could easily roll back to one that didnt give a problem.

Update about Ccleaner permissions issue.

It seems that It's entirely an CCleaner issue by itself. Tried to install CCleaner on several Vanilla W10 versions like 1809 Oktober / November and March editions. And tried also vanilla 20H2 version. They all gave me the same result.

 

[Clanger]

do you have a kind of mid-way Barebone++ with LAN Wifi Smartcard support version of a preset?

no, but someone else might.

 

[banko84]

no, but someone else might.

Clanger or Maybe Kasual or MT_ What settings should I use to disable UAC?
Is this ok? See attachment below.
Or should I just disable almost everything there is to disable?
Please also look at the registry files I integrate.

Edit: It seems that I have ripped out Guard components with removing Hyper-V. Does that compromise UAC? Is it even possible to rip out Hyper-V without breaking UAC / Security measures?

Edit: nuhi Removing Hyper-V Guest and Defender removes critical parts of the Systems that interact with UAC. Meaning it broke Copying files from one place to another. Meaning it temporeraly closed Eplorer.exe and the copy task was not completed. If having those removed without aiding tweaks to the system also copying things from another location to the Desktop, left me with a black screen and an arrow with the blue circle of death Maybe someone can reproduce this and do some fixing in NTLite?
And no. The registry files are fine when I left Defender and Hyper-V Guest in tact.

 

[banko84]

Any ideas on the above guys?
Clanger MT_ Kasual nuhi

 

[francis11]

Maybe try without your reg settings to UAC coz you change UAC settings in NTL as well.
Still my settings dont intephere with CCleaner on 20H2 or any other earlier version of W10.
I can't answer for the Hyper-V part, as i don't select this in Compatibility and delete other parts like SMB.
Also there's settings in CC to consider where you can ignore UAC prompt.

 

[banko84]

Maybe try without your reg settings to UAC coz you change UAC settings in NTL as well.
Still my settings dont intephere with CCleaner on 20H2 or any other earlier version of W10.
I can't answer for the Hyper-V part, as i don't select this in Compatibility and delete other parts like SMB.
Also there's settings in CC to consider where you can ignore UAC prompt.

UAC Prompt bypass I know off. The issue is rather that when I want to save the settings ini file.
Tick the box and this window pops up. Picture below.

This prompt is also present in totally untouched W10 1809 and 20H2 installs!

 

[Clanger]

banko84 i dont touch uac settings.

 

[banko84]

banko84 i dont touch uac settings.

Ok.

 

[francis11]

UAC Prompt bypass I know off. The issue is rather that when I want to save the settings ini file.
Tick the box and this window pops up. Picture below.

This prompt is also present in totally untouched W10 1809 and 20H2 installs!

What happen if you try run CC as admin by rightclick on CC.exe or the shortcut, maybe rightclick properties change to run as admin on compatibility tab (change settings for all users)?

 

[banko84]

What happen if you try run CC as admin by rightclick on CC.exe or the shortcut, maybe rightclick properties change to run as admin on compatibility tab (change settings for all users)?

Right Click on executable or Shortcut and Run As Admin has the same result.

 

[MT_]

From my powershell script:

# User Account Control
$Path = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System"; if(-not (Test-Path -Path $Path)){ New-Item -ItemType String -Path $Path }
New-ItemProperty -Path $Path -Name "EnableLUA" -PropertyType DWord -Value 0 -Force

Subsequently you can disable (Optional):

$Path = "HKLM:\SYSTEM\CurrentControlSet\Services\luafv"; if(-not (Test-Path -Path $Path)){ New-Item -ItemType String -Path $Path }
New-ItemProperty -Path $Path -Name "Start" -PropertyType DWord -Value 4 -Force

I'm running permanent built-in admin account, sorry I no longer give any support on stripped builds.