New
#750
New builds will also zap the Update History, so, since this is apparently still a work in progress, maybe that code is still alive to clear it.
New builds will also zap the Update History, so, since this is apparently still a work in progress, maybe that code is still alive to clear it.
All Machines that are on Insider here, Update History cleared, shows it installed properly though, so guess will fix itself at some point maybe lol
C:\Windows\SoftwareDistribution\ReportingEvents.log
{C7F18A11-516D-4BDB-A3ED-441A2B2ED644} 2018-04-10 17:10:48:620-0400 1 181 [AGENT_INSTALLING_STARTED] 101 {22524D26-20D4-4C51-9D1C-F0B1C85AD4EC} 1 0 UpdateOrchestrator Success Content Install Installation Started: Windows has started installing the following update: Cumulative Update for Windows 10 Version Next (10.0.17133.73) MPfjlgxUCkK75z3H.1.2.6.1.1.0
success here. updates from 17133.1 rs4 remained in the wu history. this, of course, is insider loads.
does this help?
I had updated a non-insider system to 17133.1 (figuring it was the final release) and ran yesterday's WU which did update MSOffice but not Win 10. I downloaded the MS 64 Bit KB4100375 file and used Brinks Install CAB file in Windows 10 TUT Install CAB file in Windows 10 and it installed the .73 update.
WEK
Please enlighten me, the first post in this thread is marked "two weeks ago", yet is dated 10 April, how come?
Installed the update on two non-Insider machines without incident.
Found a new bug. IntelliSense does not work for me in PowerShell ISE (and ISE (x86)) and the whole PowerShell crash. Same issue on 2 computers on Build 17133.73.
Have to test in a VM.