Huh? After that long time even on GitHub and the quite big delete bug is still there! Code: echo Removing OneDrive leftovers. echo --------------------------------------------------------------------------------------------------------------------- echo. rd "%USERPROFILE%\OneDrive" /Q /S > NUL 2>&1 rd "%systemroot%/Users/%username%/OneDrive" /Q /S > NUL 2>&1 rd "C:\OneDriveTemp" /Q /S > NUL 2>&1 rd "%LOCALAPPDATA%\Microsoft\OneDrive" /Q /S > NUL 2>&1 rd "%PROGRAMDATA%\Microsoft OneDrive" /Q /S > NUL 2>&1 rd "%Windir%\SysWOW64" /Q /S > NUL 2>&1 TASKKILL /F /IM OneDrive.exe /T This tries to silently delete the complete SysWOW64 folder (x86 virtualization layer). Was already reported years ago in this very thread!
Thanks for reporting this, i stopped working on this script two years ago and i missed a lot of your feedback i'm going through the comments and i'll be posting an update soon Just fixed this one on GitHub
Is this possible with this tool to disable FULL ROW SELECT in a window? More info posted here: https://forums.mydigitallife.net/th...w-select-in-latest-windows-10-possible.78291/
The geeser has returned to this thread after 2+ years... asking for support yet no one has bothered to ask him the reason for his absence..... all he has got is criticism ... welcome back mate, by all means develop the work... it is the reason why i posted the link to your GIT page in the hope that if anyone can contribute (no matter how small) , they can freely do so
For the last 2 years, I regularly use the script (v3.5) for my various Windows 10 LTSB 1607 install instances, mainly to disable telemetry, remove crapware like OneDrive and Cortana, and restore Photo Viewer In recent times, Windows 10 LTSC 1809 has different, sneakier ways of going about intrusive settings and Toggle Tweaker doesn't work with this latest version. So yes, if you are going to update the script, you have at least one supporter here!
I do that for my primary machine but the ease of use of Toggle Tweaker does serve a purpose in, for example, set up of several instances of Windows.
I'm not trying to speak bad of anyone, but in my opinion an error of this magnitude is inexcusable. I realize people aren't perfect and mistakes are made, but how can anyone who knows anything about how windows works possibly miss an error like this and then leave it in the code for what, 2 years? This looks to be intentional. Someone please explain to me how this is not intentional. In writing a script, there's no possible way I could miss an error that bad. Even if the author is copying and pasting pieces of code, in what possible scenario would you think it's okay to even attempt to delete SysWOW64? Damn, that's a bad mistake. It's the worst mistake I've ever seen in any professional batch script.
I found a bug. "Release and renew the IP address from DHCP server" option hangs on me because I have VirtualBox Host-Only Ethernet, and that is Enabled. Manually disabling it fixes the problem. Keep up the good work!