Cumulative Update KB4517389 Windows 10 v1903 build 18362.418 - Oct. 8 Win Update

Guess this is the best route, MCT and me sometimes have issues. Thanks for the suggestion.

Gort

Hewjr100 said:

Guess this is the best route, MCT and me sometimes have issues. Thanks for the suggestion.

Gort

In your case, I think you are better off using UUPDump, for there is not a .iso yet from Microsoft Download page for your version 18363:
Windows Insider - Get Latest Fast Ring ISO image

Hewjr100 said:

That is what I'll do. UUPDUMP works well. Thanks.

Gort

- - - Updated - - -



IronZorg89,Maybe so, but it is on the list.



Gort

Even better if the Microsoft's Download Page has it for Insiders. I have left the Insiders Program for a while now; that is probably why I was not aware of that. Thanks for pointing that out!. That is also why I love this forum; one gets to learn something new every day.
EDIT: I found out how to do it according to your post (screenshot) in this tutorial (OPTION FOUR) and I should have known better:
Download Windows 10 ISO File

Hewjr100 said:

I hear ya, me too. It probably will continue to fail until someone fixes it Monday.

Gort

Best way to find out is probably to try it (Repair Install) if you have the time and feel like it; otherwise, you can wait for the next CU. Keep in mind that the Repair Install would correct any glitch or corruption in your system causing the error, meaning maybe it will work. It is all up to you.

I've had Windows Update paused for two months due to Microsoft Updates flasco back in 30 August and September updates.
Today i decided to let WU to check for updates,found only three from September (NET Framework,Flash and CU for September KB4515384)

No issues so far,but im wondering why i didn't get Octomber updates too ? i checked five times and still WU tell me im "up to date"

As to using UUPDUMP for 18363 -- I have done that, and the ISO is named 18363.418.191006-1449 ... but when I open it with DISM, the build is reported as 18362.418, not 18363. I mentioned this in another post, as I was also trying to build a 18363 ISO.

Mark Phelps said:

As to using UUPDUMP for 18363 -- I have done that, and the ISO is named 18363.418.191006-1449 ... but when I open it with DISM, the build is reported as 18362.418, not 18363. I mentioned this in another post, as I was also trying to build a 18363 ISO.

I used the Aria2 feature at uupdump to create an .iso. I'm unfamiliar with using dism to check the build number, but I ran an upgrade install from the .iso, and winver reports Version 1909, build 18363.418.

It may have been of dubious value. The only change I've noticed is that my Edge bookmarks were badly messed up. (Does 1909 include the Chromium version of Edge?)

bobkn said:

I used the Aria2 feature at uupdump to create an .iso. I'm unfamiliar with using dism to check the build number, but I ran an upgrade install from the .iso, and winver reports Version 1909, build 18363.418.

It may have been of dubious value. The only change I've noticed is that my Edge bookmarks were badly messed up. (Does 1909 include the Chromium version of Edge?)

It may be a problems with DISM, as others have reported the same issue.

The command format is: dism /Get-WimInfo /WimFile:P:\sources\install.wim /index:1

Where P: is the drive letter, the sources file is either install.wim or install.esd, and index is the number of the edition in the ISO file you want to check.