Beware if you use it as a portable app you can't search the Settings only the Control Panel. For example, type metered in the search box and you will see 3 results, but only if you have Open-Shell installed (StartMenuHelper64.dll in C:\Windows\System32). P.S. Open-Shell saves its settings in the Registry, so I wouldn't call it portable.
Worked perfectly on a clean install. What I noticed that with Edge too, it is still not present in the system, I have to install it manually then. Second, in context menu, Nsudo is present, how can I remove it?
About Edge, it's likely that the image you're updating doesn't have it either. The script doesn't remove Edge when it's present in the image, but it doesn't install it if it's missing. About nsudo, I can check later. I'm traveling at the moment and will be back in 3 or 4 days.
@ashish1989 Try this reg file to remove nsudo from the context menu. It is in txt format. Rename it to .reg
Is Toolz_20230401_Repack.exe needed for the functionality of the script? I commented it out, but these are powerful apps so now I wonder did I break the script? I noticed that you have removed these lines from the "old" script: Code: :: Disable the following trackers/loggers :: Some trackers are also added to the list below in their appropriate subsections, eg. Windows Defender set DisableTrackers="AutoLogger-Diagtrack-Listener","Circular Kernel Context Logger","DiagLog","Diagtrack-Listener","LwtNetLog","Microsoft-Windows-Rdp-Graphics-RdpIdd-Trace","NetCore","NtfsLog","RadioMgr","ReadyBoot","SQMLogger","UBPM","WdiContextLog","WiFiSession" It's not mentioned in the changelog, do you remember why?
Toolz_20230401_Repack.exe (setacl, nircmd and nsudo) is not needed for the functionality of the script. It was added to install some repacks where they are needed. I don't remember why I removed this line. Since I'm traveling, I can't verify my observations. But it has to do with something that was breaking the Store installation or digital activation. But in any case, put these lines back in the code and test with your image and see what happens.
Updated to SD10v202_42 [1904x.5073] https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/
Hello, when I try to open the start menu it says: "Critical Error – Your Start menu isn’t working. We’ll try to fix it the next time you sign in". with the previous version got the same error older scripts worked fine for me. is there a way to download older versions of the script? thank you for your work.
Sorry no, just reinstalled my system. I also noticed that under control panel > user accounts you can't add users or edit them the buttons are disabled. In older versions it worked fine. Just letting you know.
In this latest version, installed in Virtualbox, I captured these images. Is this what you are talking about?
But here they are working. They are not gray. Note that the script has not been modified in its essence. It only includes W10UI for the integration of updates and I adjusted some items to apply or not, but nothing has been changed. I can examine timesync, because the script adjusts it. I just don't know if it enables or disables it. I'll take a look. By the way, which script are you using? with or without edge?
Without, I noticed that (cp/user) because of the start menu not working, read as one possible solution to create another admin account and switch to it.