Windows 10: Manually downloaded KB4048955 could not be installed.

2017-11 Cumulative Update for Windows 10 Version 1709 for amd64-based Systems (KB4048955)

Two days ago, Windows Update MiniTool found the above update.
Yesterday, I downloaded it from Microsoft Update Catalog
Today, when I tried to install the downloaded update (a .msu file), it said KB4048955 was already installed, but MiniTool could still find the same update, showing that it was actually not yet installed.
Then I clicked on the 'install updates' button on MiniTool, and it was installed successfully.

Does anyone know why I could not install it via the .msu file?
Is it impossible to manually download the update which can be installed successfully?

:)

 

After latest update to Ver 1709 (OS Build 1629, 64) I lost lot of system capabilities.

Could you try installing the latest Cumulative Update KB4048955 (OS Build 16299.64), which is known to fix many of these problems?

You can manually download it at:

http://catalog.update.microsoft.com/v7/site/Sea...

You can then follow the instructions in the following article install it:

https://www.groovypost.com/howto/manually-insta...

 

2017-11 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4048954) FAILS

Could you try installing the latest Cumulative Update KB4048955 (OS Build 16299.64), which is known to fix many of these problems?

You can manually download it at:

http://catalog.update.microsoft.com/v7/site/Sea...

You can then follow the instructions in the following article install it:

https://www.groovypost.com/howto/manually-insta...

 

If you get a .msu file you need to use the windows update installer, wusa.exe to install that package. Here's a description of that program, aka the Windows Update Standalone Installer, along with instructions on its use from MS: https://support.microsoft.com/en-us/...ler-in-windows. .msi files execute on their own, .msu files do not. That's probably where your gotcha came into play!
HTH,
--Ed--

 

Last month, I did successfully install two .msu files without knowing/doing anything about wusa.exe, so I think the problem did not lie in wusa.exe.

 

Matthew,

You can look at your update records in Event viewer -

1 Applications and services logs, Microsoft, Windows, WindowsUpdateClient, Operational, Events - 41, 31 {41 = successful update downloads, 31 = update download failures}

2 Windows logs, Setup {this records particular updates but not them all; it includes Event 4 restart warnings and Event 2 installation successful}

3 Windows logs, System, EventSources - WindowsUpdateClient, Event - 19 {update installation successes only}

Notes
- I find the presentation of #3 quite easy to export then work with because the description pane's General tab identifies the update concerned [whereas #1 forces you to dig inside the Details tab and that tab is not exported].
- Note that #3 includes updates to Apps making it, as far as I have been able to find out, the only place where App updates are identified.
- I only find #2 useful if I'm chasing down problems after having found an update listed in #1 but not in #3.
I do not yet understand what gets included in #2; no pattern is apparent.

By the way, I always download updates from the MS update catalog. Cumulative updates are always msu files. You can just double-click on them to install the update i.e. they just execute on their own so there is no need to take any other action.

Denis

 

Dear Matthew:
You may very well be right. But I've had sporadic trouble with .msu files when applying them manually myself, and in the two cases where it's occurred on one of my Windows PCs, it's been wusa.exe related. I could indeed have erred in generalizing my experience to your situation. Sorry for any confusion or consternation caused thereby. I hope you get it sorted soon. Thanks,
--Ed--

PS: Try3 is correct about double-clicking the .msu file to launch it automatically. You only needed to invoke wusa.exe on older Windows versions. I just confirmed for myself that any .msu file invokes that program automatically whenever you double-click any .msu file. I was wrong in asserting that the program had to be invoked explicitly, because it's invoked automatically. My apologies for the misrepresentation.

 

I found that I had already installed KB4048955 in November.
However, four days ago, on 10th, Windows Update MiniTool found KB4048955 again, as shown in this post.
On 11th, I downloaded KB4048955 again from Microsoft Update Catalog, and the downloaded .msu file was exactly the same as the one I downloaded and installed in November.
So, when I ran the file, it said '(KB4048955) is already installed', but MiniTool could still find KB4048955 as a pending update. Then I clicked on the 'install updates' button, and it was installed successfully.

Does it mean that the latest version of KB4048955, which was found by MiniTool, cannot be manually downloaded from Microsoft Update Catalog, so that I could only install it via MiniTool?

 

See below: Code: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 11/12/2017 20:00:08 Event ID: 19 Task Category: Windows Update Agent Level: Information Keywords: Success,Installation User: SYSTEM Computer: DESKTOP Description: Installation Successful: Windows successfully installed the following update: 2017-11 適用於 amd64 系統 Windows 10 Version 1709 的累積更新 (KB4048955) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945A8954-C147-4ACD-923F-40C45405A658}" /> <EventID>19</EventID> <Version>1</Version> <Level>4</Level> <Task>1</Task> <Opcode>13</Opcode> <Keywords>0x8000000000000018</Keywords> <TimeCreated SystemTime="2017-12-11T12:00:08.183530200Z" /> <EventRecordID>4390</EventRecordID> <Correlation /> <Execution ProcessID="3420" ThreadID="7444" /> <Channel>System</Channel> <Computer>DESKTOP</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="updateTitle">2017-11 適用於 amd64 系統 Windows 10 Version 1709 的累積更新 (KB4048955)</Data> <Data Name="updateGuid">{F5E66353-789D-46F4-8412-6BFD0818A4F8}</Data> <Data Name="updateRevisionNumber">1</Data> <Data Name="serviceGuid">{8B24B027-1DEE-BABB-9A95-3517DFB9C552}</Data> </EventData></Event>[/quote]

No apologies are needed. *Smile

 

Matthew,

No, there is no such limitation. I downloaded KB4048955 from the MS update catalog then installed it manually.

Denis

 

I did the same in November, but I could not do the same a few days ago.

 

This may be kind of far off the beaten track, but there is another way you can try to get the update installed. By taking the image offline (this requires another computer, or another OS into which you'll boot on the same machine), you can use DISM to manually install an update. See this MS Hardware Dev Center article for the details: DISM Operating System Package (.cab or .msu) Servicing Command-Line Options | Microsoft Docs.
HTH,
--Ed--

 

Matthew,

Do you realise that cumulative updates are just that, cumulative? KB4054517 is now the only one you will find using your update checking tool or need to install.

They all remain available in the MS update catalog but only the latest one is required.

Denis

 

I installed KB4054517 yesterday, and now it is 16299.125.

Assuming I want to back up cumulative updates for future re-installation of Windows, do I only have to back up the latest version, which will include all necessary updates issued previously?

This is far too complicated for me.

 

Matthew,

Yes, the latest cumulative update is the only cumulative update you need.

I have never seen anybody test the notion that the latest Flash player & MS Malware Removal Tool updates are the only ones required for those components.
- I am not at all sure about Flash player updates but the info page for the November update, just for example, does not identify any prerequisites so I think that means that only its latest one is required.
- In the case of the MS MRT, my understanding of its info page [https://support.microsoft.com/en-gb/help/890830] is that only the latest one is ever required.

Denis