mr x I had found your second link yesterday not the first. mood thanks for searching now I wonder how is Huawei tied to MS if at all or is it just the way the mini tool shows it? why doesn't it show up in device manager and why doesn't it show in Windows update? also while I was searching yesterday before finding the same named company that makes phones, I came across the one the NSA was watching and breaking into. is this the company? Huawei's Devices division provides white-label products to content-service providers, including USB modems, wireless modems and wireless routers for mobile wifi,[80][81] embedded modules, fixed wireless terminals, wireless gateways, set-top boxes, mobile handsets and video products. Huawei was founded in 1987 by Ren Zhengfei, a former engineer in the People's Liberation Army https://en.wikipedia.org/wiki/Huawei when you look at the list of partners, you will be very surprised Symantec, Motorola, and the list goes on.
Well I think WUMT made a good job finding M$ hidden/hardcoded hardware at people's sight. Just untick it and keep updating the rest of.
I get suggestions of 3rd party updates (drivers) via normal windows update....As said by Mister X the option to ignore them exists in wumt.
"Well I think WUMT made a good job finding M$ hidden/hardcoded hardware at people's sight." and I think that is great. from some of those sites I found other people finding the same entry with other similar software. it just worries me it is there lurking for whatever reason, that's all.
"Then stop using it. Fair enough, no?" mr x you misunderstood me I think. I didn't say the mini tool was bad, I just meant finding that driver on my system and not knowing what it is disturbs me.
Your hardware has no relation to Huawei and you are not sure why you have this update in the list, so the best solution is to skip this firmware update.
mood I understand that but can you tell me why other software has been detecting this as well? any found the ms link and will stop posting about it. http://www.catalog.update.microsoft...updateid=2a98c83a-2e9d-4a36-bced-69ac984589b3 lets get on with talk about the topic
For reference for anyone else with the same issue....Using WUMT the updates for "other MS products" downloaded & installed without any issues. Unfortunately, I spent hours trying other suggestions that didn't work before trying WUMT
I have been wanting the feature where wumt automatically stops and disables the windows update service when it exits. While we are waiting for that functionality to be in the program, I put together a command script that will do it. It is in the code section below. It uses a trick I found on stack exchange to make a vbscript command to request admin privileges. Then it runs wumt_x64.exe. Once wumt closes, it will automatically disable and stop the windows update service. I could have had it automatically start the service before it ran wumt, but I find that initial prompt of wumt asking me if I want to start the service comforting. To use it, copy and save the script to something like "wumt.cmd" and make sure that file is in the same directory as wumt_x64.exe then run it. I also happen to use Windows 10 Home, myself, and since group policy is useful for changing wumt's behavior, I found this link on how to add group policy editor to Windows 10 home. Code: @echo off set "batchPath=%~0" for %%k in (%0) do set batchName=%%~nk set "vbsGetPrivileges=%temp%\OEgetPriv_%batchName%.vbs" setlocal EnableDelayedExpansion :checkPrivileges NET FILE 1>NUL 2>NUL if '%errorlevel%' == '0' ( goto gotPrivileges ) else ( goto getPrivileges ) :getPrivileges if '%1'=='ELEV' (echo ELEV & shift /1 & goto gotPrivileges) ECHO. ECHO ************************************** ECHO Invoking UAC for Privilege Escalation ECHO ************************************** ECHO Set UAC = CreateObject^("Shell.Application"^) > "%vbsGetPrivileges%" ECHO args = "ELEV " >> "%vbsGetPrivileges%" ECHO For Each strArg in WScript.Arguments >> "%vbsGetPrivileges%" ECHO args = args ^& strArg ^& " " >> "%vbsGetPrivileges%" ECHO Next >> "%vbsGetPrivileges%" ECHO UAC.ShellExecute "!batchPath!", args, "", "runas", 1 >> "%vbsGetPrivileges%" "%SystemRoot%\System32\WScript.exe" "%vbsGetPrivileges%" %* exit /B :gotPrivileges setlocal & pushd . cd /d %~dp0 if '%1'=='ELEV' (del "%vbsGetPrivileges%" 1>nul 2>nul & shift /1) :::::::::::::::::::::::::::: ::START :::::::::::::::::::::::::::: start /wait wumt_x64.exe sc config "wuauserv" start= disabled sc stop "wuauserv"
New version: 20.12.2016 Changelog: v20.12.2016 - Fixed a small issue when Automatic Updates is set to Disabled. Code: https://wumt.blogspot.mx/2016/11/windows-update-minitool.html
If you are copying things, written by other people, and publish these as they would have written by you, then you're just a brutal thief. Stop such a stealing. Original script is here Here is owner's comment Spoiler This is just a simple script that copies files. What's the big deal? I wrote the WUMT wrapper Script and then somebody stole it here. It's just a simple script that turns the windows update service on, runs WUMT, then turns the windows update service off again so you can do manual Windows updates without registry changes in case Microsoft removes registry update control in future updates. Do you think I care? No I don't. I give it away freely for anyone to copy and modify as they wish. If I write a simple script like that, what's the big deal? It's not like I wrote a proprietary piece of software that took hundreds of man hours and a team of experts and thousands of dollars. It was one person writing a simple script, like you said you did. Would I threaten someone? NO! I would never dream of it over something as simple as what you or I did. I don't know what the hell your problem is. If you want to contribute, then contribute. If you want to make it proprietary then compile it into an EXE, copyright it, and STFU. Damn. Source
Clearly not a carbon copy, and he even went through the effort of writing out his own understanding and explanation of the script that he wrote. This isn't a blatant copy and you're coming off like an idiot.
A few times WU has started to look for & download updates while I'm already installing them with WUMT. This seems to screw things up - any way to prevent it?
Disable Windows auto-checking for updates. Code: schtasks /Change /TN "Microsoft\Windows\UpdateOrchestrator\Schedule Scan" /Disable ren "%WinDir%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator\Schedule Scan" "Schedule Scan.bak" md "%WinDir%\System32\Tasks\Microsoft\Windows\UpdateOrchestrator\Schedule Scan" schtasks /Change /TN "Microsoft\Windows\UpdateOrchestrator\Schedule Scan" /Disable schtasks /Change /TN "Microsoft\Windows\WindowsUpdate\Scheduled Start" /Disable ren "%WinDir%\System32\Tasks\Microsoft\Windows\WindowsUpdate\Scheduled Start" "Scheduled Start.bak" md "%WinDir%\System32\Tasks\Microsoft\Windows\WindowsUpdate\Scheduled Start" schtasks /Change /TN "Microsoft\Windows\WindowsUpdate\Scheduled Start" /Disable
Another option pointed out to me on "tenforums" - set WU to notify only http://winaero.com/blog/how-to-disable-windows-update-in-windows-10-rtm/
after not updating win7 for a long time, probably over a year, I read thrue all these threads related to that. great stuff. I started using update minitool and it's working great but on one machine I get option to chose windows updates and microsoft updates, but on the other only windows update. Anyone knows a reason for this? maybe some specific KB missing? thanks.
I have a strange issue that maybe I missed reading here, but I did not see it. I have Win10 Pro 64-bit 1703. I use to have 1511 and I used the WUMT to handle all my updates including my Office 2010 by using the option "Microsoft Updates" in the drop-down. But I did a clean install of 1703 along with my Office 2010 and when I unzipped WUMT 20.12.2016 I noticed something. After I launched the program I went to set my settings and under "Update service" I had it set to "Microsoft Update" with my 1511 system. Now in 1703 the "Microsoft Update" option is no longer listed. I have only three options and I am on Windows Updates. But this only gives me the Windows 10 updates, did I mess something up or does WUMT not play well with 1703? I did activate Windows 10 and Office and confirmed that they are activated. So something strange and I cannot get Office updates to appear. Again maybe this is an issue and I missed it in the 6 pages here so if someone can point me to the thread, that would be great. But if not, I would like to find what I may have done wrong or if this is by design. Thanks
I am running Windows 10 (x64) version 1703 (15063.540) and just opened WUMT and saw both "Windows Update" and "Microsoft Update" as choices. However, please be advised that I probably have an older version of WUMT as it is 20.12.2016. I need to go find a newer version.... EDIT: It appears I might have the newest version of WUMT?!