I always welcome suggestions, ideas, and requests. Your suggestions will be added to the next version's (v2.4.9) uninstaller. Thanks for helping make it better.
@pf100 2 years ago when you first released this back in 2016 (at least that when I recall being made aware of this development), I knew exactly how hard it would be to maintain this since Microsoft annoyingly changes how Windows updates or what updates, seemingly forever. I am pleased and very grateful that you continued to work on this and I just wanted to thank you for sticking to it. It is very much appreciated and your work never did go unnoticed.
@Lars220, thanks for the info. This is exactly the kind of thing I look for. These updates are update hijackers. I don't know about the first two files yet, but from what I've found out so far, sedsvc.exe appears to be in the c:\program files\rempl folder. The script already renames that folder every time you run it, so people using the script should be okay for now. I'll do more research and report what I find, and will update the script for these new update hijackers as soon as I can install these updates on a 1709 VM to analyze it. And 886,664 bytes = 866.664 thousand bytes = 866.664 KB = .867 MB. These are small files.
A potential risk exist when creating the xml files and the directory names contain "exotic" characters (é, è, ...). This can be alleviated with the following changes : Replace lines 335 and 415 (script 2.4.8) by : Code: )>"%temp%\%Task_Name%.xml"&cmd /u /c type "%temp%\%Task_Name%.xml">"%~dp0%Task_Name%.xml del /q "%temp%\%Task_Name%.xml" >nul 2>&1 Example : Before : <Command>"C:\T‚l‚chargements\WUMTWrapperScript\Portable\WUMT Wrapper Script\wub.exe"</Command> After: <Command>"C:\Téléchargements\WUMTWrapperScript\Portable\WUMT Wrapper Script\wub.exe"</Command> Update : In fact is doesn't work when "special" characters appear in the path name.
Thank you for being such a huge help for those with non-english windows @rpo, as well as other major contributions you've made. Your changes will be in the next version 2.4.9.
ich had a maschine with 1803.112 last night, second time i had this kind of intense experience dealing rempl in heavy action! i realized a new "system" account was created added with ultra privileges. (wumt wrapper 2.4.8 was properly installed and active on this maschine!) it messed my friday night.. (remotesession) because i had almost no rights to do anything, startmenu, win+r not working, taskbar unresponsive, i transferred some cmd files to the maschine, most important one was a simple .lnk file preset admin rights, with comspec target so i got an elevated prompt. i ran another cmd to activate the administrator account and was able to reboot in this one. with working elevated prompt i deleted the most destructive tasks that where running, one had not even a senseful name, it was a mix of ascii code.. after getting really pissed of once more by rempl i began to save log files, proofs of what was going on, i always do this since microcrap started even destroying computers, ssd's and hdd's. in this damn situation i began messing some things up, deleted some systemfolders, files, tasks, takeowned some others and the situation cooled down. (after some hours) it is absolutely fact that microspace is flooding your fly-out experience with highly responsive shims. folders you know there ARE important files and logs in there, become empty in a fifth of a second when you throw an eye on them.. it does not matter where the s**t was stored til winblows ten showed up. when messing up or block the "software distr." or "usostore" in %programdata%, the unstoppable s**t will be placed in yet another location. the reason why the waste and crap that ms uploads to our devices is that massive is to slow the user (maschine owner, victim) down! oh, you should not be here, lets compress some gigabytes of your most valuable photos so you, in your userspace won't move. is that clear enough? mr. anykey.... ich will never ever forget or forgive what this club of individuals does and did, they even tried to f**kgrade my own maschine, without success, i still use a special, stable build of the 1607, i already have completed fully updated install images but i... just see that the build i'm already running might be the last one someone would call "usable" are some logfiles useful for you?!! if so i upload some stuff! however, without your work i wouldn't have made it "here", so far. what ms does is a crime! most people are ignored an simply disrespected, REMPLED, and not wanting a completely remoted piece of toxic garbage they even paid for.. as their pc. me included!!! what they do is a total discharge, would never have imagined things will be or get worse then right now. sorry for strong words! this even too soft to give a picture how it feels like to deal with such AI crap.
I'll fix it. You helped a lot and gave me enough info to fix the rempl problem in the next version. If you find anything else just let me know. I should have taken @s1ave77's advice months ago about not just renaming the rempl folder in the script, because in your case it recreated itself. So I will take a different approach and deny system access to the rempl folder and files instead. In the next version rempl won't be able to run and it won't be able to recreate itself.
Just wanted to post the following code that I'm using for personal use to disable the tasks, in case it's of interest: Code: for %%? in ("%systemroot%\System32\Tasks\Microsoft\Windows\WindowsUpdate\*") do schtasks /change /tn "Microsoft\Windows\WindowsUpdate\%%~nx?" /disable
powershell is just a UI for cmd, and it needs conhost to work ^^ aaand there is a file without an ending (filetype) in the powershell folder you have to (find hehe) delete to disable sending telemetry data to microslop. isn't it great? all these "benefits"?!... i will upload the .etl log files of rempl in action. maybe this helps. thanks alot @pf100 for keeping on!! greetings!
I wasn't aware there was a problem with the script in a path with special characters (é, è, ...) until @rpo brought it up a day or two ago. I can only read english so I can't test the script in a foreign language which is very frustrating. The problem is that the tasks created by the script have corrupted path names with special characters (é, è, ...) "C:\T‚l‚chargements\WUMTWrapperScript" instead of "C:\Téléchargements\WUMTWrapperScript" and I can't can fix it in time for the next version since the new "rempl v2" is out in the wild now and I need to push out this update. I'm going to need a volunteer to test code in folders with special characters so I can fix this or pointers to testing it myself. I figured out how to do it. So the solution for now is: Don't install the script in a path with special characters. If you have a foreign language version of windows, install the script in the root of the drive, or make sure your wrapper script path has no special characters in it. Edit: I can now test special character paths so I'm going to attempt to fix it before the next release. If not by then, the release after that. Fixed!
so i guess the spaces in install folder name should be taken away also. the mean thing is, microdrop tolds us on and on what's coming, but not clear enough to respond. special characters like "bitcoin" and "smileys" where mentioned in the update history some weeks ago. greetz
Spaces in the path name is okay and is working fine. Special characters in the path name is the only problem. Edit: I just now fixed the special characters problem. Command script does not work with unicode well. I reused some old vb script task creation code @rpo wrote for script v2.3.1. Some clean-up work and documentation edits and v2.4.9 will be done. Yay!
August 14, 2018 WUMT Wrapper Script 2.4.9 *Disables rempl v2 *Improved uninstaller. Now gives the option to open network connections to disable the internet before uninstalling. *Extensive testing for stability and bugs. *Tasks creation by vbscript provides some support for special characters in path name in some languages. No cyrillic, haven't tested chinese, japanese. French works, so german, spanish and portuguese characters in path should too. If in doubt, put script folder in path without special characters. Spaces are okay. You can verify the wdu and wub_task tasks execution parameters to see if the path looks okay, otherwise the tasks won't work. *Thanks for the code contributions and suggestions by @rpo, @Lars220, @Whistler4, @app_raiser and @RazTK
can't and won't wait any longer. updated the portable script by myself! thanks again for staying awake! ;-) - - - - - there are some things i have to mention about these update "issues": first: i guess this new hidden "create unelevated explorer task" might become an issue soon! even more because it seems no longer possible to pin scripts to the startmenu or to taskbar, i bet microslop will further punish user rights and delete options to run "things" elevated. second: i would not bet a chicken egg there are still humans with feelings and so on in redmond, but, if a huge update in these days on an old build won't install, i would take that very serious! this is a warning very easy to oversee. there is no turning back. i was thinking about installing the very same update (2248) on my holy 2156, but i never ever will! it's to late, garbage, last messed up (revision) on july 11th or even later now. they delivered us a lot of time bombs (zone issues) which aren't exploded yet... my opinion / experience - - - applied the wumt script update successful on 3 machines yet!