"Mountvol" lists all available volumes and their mount points, you could use that instead of iterating A-Z. Or PowerShell Get-Partition (if PowerShell is available).
Not to beat a dead horse, but I just want to confirm that 2.5.5 did work fine to update the computer that 2.5.6 wouldn't boot after 2018-12 CU. I installed 2.5.5 after image restore and success.
I'll check out mountvol. Didn't know about it. Powershell is not available in standard install media WinPE or Windows Recovery Environment. Thanks for sticking with it and being a big help pinpointing exactly what was going on. You cut my diagnostic time in half, at least. I can now forget about this fiasco for a couple of days and get some sleep tonight. This bad situation will make the script better in the future because there'll be a BSOD recovery plan in place if this ever happens again.
Thanks for this. Had a problem booting one of my two 1803 PC. Thankfully I came here before getting around to re-boot my other PC. Thanks for the help in getting everything back to normal.
Is there a way to make WUMgr display the updates that are missing and need to be downloaded and installed after it has finished analysing a system? That is my only problem at the moment the way it has been set up.
I use WuMgr a lot but don't understand what you're asking. I'll do my best to help but you might have better results asking in the WuMgr thread since the author of WuMgr lives there.
The poll has spoken. Both WUMT and WuMgr will remain as options in the script until a majority asks me to remove one.
Great! The only downside I can see is one extra screen, meaning, hit "c" then "1" or "c" then "2". Easy.
Hi pf100, Thanks for the reply. Please ignore my query. I have not been able to replicate the problem since reverting to 2.5.5. I will let you know if I encounter the problem again. Cheers, TheFly.
@thefly42 intermittent problems are the worst. @Whistler4 speaking of intermittent problems, has 2.5.5 solved the task creation error thing? Because I made some changes and am wondering if they were effective. When I get to that screen I like having a choice. I almost always pick WuMgr but it's nice to know I can use WUMT too.
I think you fixed the task creation error because I haven't seen it again. My sentiments exactly about the choice screen, but like you, I almost always pick WuMgr. Sometimes I choose #2 just to see if there's a difference. I like the ability to choose.
Anyone else experiencing problems? I seem to get stuck on downloading a certain update ("2018-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4103720)"). I've tried it with both WUMT and WuMgr multiple times. I also tried both the "download" and "install" feature, but I always have the same issue. Any ideas on what I can try?
just install the update; when you run WuMgr after completing the update it will be detected so it won't come back as available update
Create a folder with short path, i.e. c:\update and copy the CAB file to it. Then in admin CMD (make sure the bolded name matches your CABs name): Code: dism /online /Add-Package /PackagePath:c:\update\windows10.0-kb4103720-x64.cab
Thank you both very much, s1ave77 and Skunk1966. I did exactly what s1ave77 suggested and it worked perfectly. After I installed it manually, the other updates worked just fine with WuMgr. Again, thank you both very much Quick follow-up question: can I safely delete the contents inside "C:\Windows\SoftwareDistribution" after I successfully installed the updates? Or are there other important files inside that I shouldn't delete?
@hansmeierone This is the easiest method to install updates that won't install when using the script: 1) Don't close WuMgr or WUMT after it fails, just recheck for updates with WuMgr or WUMT but don't install updates. 2) Make sure any updates you don't want are hidden, then leave WuMgr or WUMT running because if you close it you can't update. 3) Go to Settings > Update > check for updates (only the updates you haven't hidden will now install). 4) After the updates are installed you can close WuMgr or WUMT, or just reboot if needed and the windows update service will be disabled automatically when you reboot. This only happens about twice a year. Let me know if this fixes the problem.