I have seen that, too. Obviously, wumgr checks for multiple processes of itself. Unfortunately, when it has to ask for Elevation, the old non-elevated process stays up a little, and the new elevated process fails to run. Short-term workaround: Right-click the executable and select "Run as Administrator". This will ask for Elevation before the process is started. @DavidXanatos needs to adjust the check logic a bit (e. g. store the PID for the original process and ignore it when checking).
I already ignore it, but @Carlos Detweiller is using the UAC bypass and this is why it fails, it will be fixed in the next release (this weekend), the issue is that an instance starts without admin rights and than starts an instance as admin through the task scheduler. so far so good. now the new instance checks for running instances and BAM finds the non admin one which started it, and that is the issue. When the process is started as admin it already has admin rights and does not invoke the UAC bypass method.
No, UAC Bypass is OFF. I never use it and get the error, nonetheless. I can only guess that WuMgr detects itself after asking for Elevation (through the standard run-of-the-mill UAC prompt in Windows 7 x64). I'm using a higher level of UAC prompt, though, so that could have something to do with it. If you want to test, move the UAC slider all the way up, then set the following Registry key: Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\CredUI] "EnableSecureCredentialPrompting"=dword:00000001 Just remove the Registry entry and revert the UAC slider when you are done.
I did not find any of these issues when testing moved UAC slider all way up added the reg key still no issues so moved everything back as it was still no issues.
So, it's likely a timing issue/race condition, not occurring on all systems. My CPU is constantly loaded at 80-95% (Distributed Computing), and I have mechanic hard disks.
Give us a break. David's program is better than yours and it is Opensource and it is being updated. When was the last the last time that you updated WUMT?
My response was to Shewolf and/or stupid user. Please see message that I quoted above mine that was posted by Shewolf. My response was not directed at you or David. Sorry for the confusion. Michael T
@shewolf is not "stupid user". Don't matter who replies to your comments or anyone comments, sometimes.
I updated my post. Maybe my update will make someone happy on not. To me it doesn't matter who wrote WUMT, which I have used ever since it was released; however, now that wumgr is out there we have a choice. Use, support, defend, whichever one you want. Michael T
@DavidXanatos I made v2.5.3 of my script so at the very bottom of the script it can be easily edited to use WuMgr. Code: Start "" "%wumt%" -update "-onclose close.cmd" ::If you want to use WuMgr instead of WUMT, insert rem (space) at beginning of WUMT line above, and un-rem the wumgr.exe line below. rem Start "" wumgr.exe -update -online 7971f918-a847-4430-9279-4a52d1efe18d -onclose close.cmd No hurry, no pressure, just saying I'm ready whenever you are. Please take your time.