Cumulative Update KB4100403 Windows 10 v1803 Build 17134.81 - May 23

f14tomcat said:

I believe you, but what does WINVER show? Hold Win Key, and type "R", then WINVER,
and enter.....

The update has now finished, so this may be moot, but winver says 1803, too.

What's happened now is that 3 days ago I deleted the stuff in the temp folder, all 50+ GB or whatever it was of it and now, 3 days later, my temp folder is back to 53 GB. The exact same size as before I deleted everything, I believe.

I had a nice clean install and when 1803 updated from 17134.48 to 17134.81 I had a Windows.old folder with about 16gbs. I don't like in-place upgrades. I'd rather clean install from latest ISO and re-install my software. How can this be prevented in future. I had no idea going from .48 to .81 was a "major Upgrade"

Barefoot said:

I had a nice clean install and when 1803 updated from 17134.48 to 17134.81 I had a Windows.old folder with about 16gbs. I don't like in-place upgrades. I'd rather clean install from latest ISO and re-install my software. How can this be prevented in future. I had no idea going from .48 to .81 was a "major Upgrade"

Update from .48 to .81 is not consider either in-place or major upgrade.

To clean install a 17134.81 you can start from a USB of 17134.1 and choose update at the beginning selection of the installation or update later after the 17134.1 is done.

Alfred001 said:

The update has now finished, so this may be moot, but winver says 1803, too.
What's happened now is that 3 days ago I deleted the stuff in the temp folder, all 50+ GB or whatever it was of it and now, 3 days later, my temp folder is back to 53 GB. The exact same size as before I deleted everything, I believe.

I noticed a similar issue since installing this cumulative update last week. The update itself installed without issue but the free space on my 1 TB Samsung EVO 850 SSD has gone down from around 90 GB to 52 GB over the last week. I do have a number of games installed on this drive, including Final Fantasy XV which uses a whopping 150 GB, but as far as I am aware none of the game installed on this drive have been updated to explain the loss of 38 GB.

I checked Settings > Storage as there is an option there to clean the temp folder. It showed a 13.1 GB of Delivery Optimization files but despite several attempts to remove them they stubbornly stay there. Disk Clean-up shows the same thing but, again, I am unable to remove them. Not sure what these are for although a 20 GB update did download for State of Decay 2 but I'm sure this is installed on my H drive, not the C drive. Microsoft being Microsoft though, I would not be surprised if the Windows Store keeps its files on the Windows drive as opposed to the drive where the games are installed (like Steam does for example).

The update kb4100403 on windows 10 x64 v1803 provides a black screen with a cicling blue dot on the place off the mouse pointer. I cann't boot the PC in a normal way. Every time a black screen and no logon screen, with time and date.
I donn't had issues with Cum. upgrade 1803 in PC's without SSD nor with SSD.
After the update some PC's without SSD have now after update kb4100403 a black screen issue.
There is no access to the user interface on the monitor.


Checking with USB-Stick with Windows 10 x64 v1803 shows HD's healthy, no issues.
The HD C;\ with windows 10 boot, shows up in the screen, without HD errors.

I cann't roll back to previous windows 10 version 1709, I have no access to the PC.
Can I do an in place install of 1709 from a USB stick windows 10 x64 1709 manually without reinstalling applications.
No restore points were set, before install of 1803.

With command prompt (Admin rights)
With command: bootrec.exe with options /FixMbr /FixBoot /ScanOs /RebuildBcd the responses are:
Fixed, No access, No windows found.
With diskpart check HD's seem to be OK.
Different partition mgrs show also: OK.

What causes this problem and can it be resolved.
It happens on different PC's.
And more people come with the same problem.

This is not what one expects for a quality update.

I have a very strange disk space issue. I don't know when it first appeared (I'm on 17134.81 now), because I never looked at settings/system/storage. Just did, since it was mentioned in #126. Anyway, my C: drive, which is my Windows System drive, is a 128 GB partition. 'Storage' shows it as 436 GB! It shows 357 used, and 79 free (which is the correct amount of free space). It shows 329 in System&Reserved. Disk Manager shows C: as a healthy and happy 128 GB partition.

Does anyone have a clue as to what might be going on?

Daz1967 said:

I noticed a similar issue since installing this cumulative update last week. The update itself installed without issue but the free space on my 1 TB Samsung EVO 850 SSD has gone down from around 90 GB to 52 GB over the last week. I do have a number of games installed on this drive, including Final Fantasy XV which uses a whopping 150 GB, but as far as I am aware none of the game installed on this drive have been updated to explain the loss of 38 GB.

I checked Settings > Storage as there is an option there to clean the temp folder. It showed a 13.1 GB of Delivery Optimization files but despite several attempts to remove them they stubbornly stay there. Disk Clean-up shows the same thing but, again, I am unable to remove them. Not sure what these are for although a 20 GB update did download for State of Decay 2 but I'm sure this is installed on my H drive, not the C drive. Microsoft being Microsoft though, I would not be surprised if the Windows Store keeps its files on the Windows drive as opposed to the drive where the games are installed (like Steam does for example).

have you tried to run disk cleanup with elevated privilege, i.e.
-click the Windows orb at the far bottom left
-Type "Disk Cleanup" and hold ctrl + Shift keys while clicking on Disk Cleanup
-You should have a window like the following:



If this approach is still not working, you can try those DISM command lines, after running first sfc /scannow:

- Dism.exe /online /Cleanup-Image /restorehealth
-dism.exe /Online /Cleanup-Image /AnalyzeComponentStore. This one gives you a result on whether or not to clean the component Store. If it says "Yes", then you should run:
-dism.exe /Online /Cleanup-Image /StartComponentCleanup

I hope this helps you in resolving your issue.