Windows 10 v1803.. manually install KB4100375 (OS Build 17133.73)
-
Thanks :) I'm learning a lot at the moment.
I'll probably reinstall again when the real deal is finally released, however up until then I may as well treat all this as a learning experience and enjoy the ride.
-
-
Thanks :) I'm learning a lot at the moment.
I'll probably reinstall again when the real deal is finally released, however up until then I may as well treat all this as a learning experience and enjoy the ride.
Same here.
I found a way to integrate KB4093110 and KB4100375 into an ISO using MSMG ToolKit 8.2. I couldn't get it to work using NTLite.
Run dism /online /get-packages in cmd, or SYSTEMINFO.exe in cmd to check for installed updates.
-
Thanks :) It sounds like you are further ahead than I am.
-
-
If you're Build is 17133.73, then you were successful. I'm not an Insider either but Windows 10 1803 build 17133 is the official version of the Spring Creators Update.
So, I will not reinstall the official release which might not include this update but use WU to install/ update any new files.
Then I would use the updated MCT to create a bootable backup install media and an ISO to have on-hand for an In-place Repair upgrade, if necessary.
MS is making a new RTM (17134) but you know this is still an (Insider Preview) right? :/ can it give me problems/issue's if i further use this (Insider Preview) .. because this is not the final RTM i think..
-
Nah - there is a bug of some sort. I do not get it listed and I did it by the normal update service.
-
-
The likely RTM build will be 1803.17134.1 (redstone4 current canary)
The 1804 is the time it was compiled on the 10th April 2018 (180410) :)
-
You are confusing the build number with the release numbering. All Insider versions leasing up to release are given the release number 1803 but have different build numbers. It is unlikely the 1803 would change. 1709 was released in October 2017 for example.
-
-
1709 was released in October 2017 for example.
True, but the build 16299.15 that was released was compiled at the end of September, hence it was still officially '1709'.
17134 wasn't compiled until April so it that were to be the release build and MS want to stay consistent in their naming policy, would have to be called '1804'.
-
Same here.
I found a way to integrate KB4093110 and KB4100375 into an ISO using MSMG ToolKit 8.2. I couldn't get it to work using NTLite.
Run dism /online /get-packages in cmd, or SYSTEMINFO.exe in cmd to check for installed updates.
Confirmed fixed in the latest NTLite beta, to be released tomorrow.