It won't change anything noticeable to the average user. Essentially this is the same thing as the version 2004 from over 2 years ago. The real feature update with new features is Windows 11.
@Enthousiast can you try to explain to me why this KB still shows up in the Windows update, although it was clearly integrated using W10UI, ? windows10.0-kb5017380-x64_df4c797cb435503663acb5f5fd48341ea845d334 Thank you
It happens quite a bit with CUs on images your build yourself. If you check C:\Windows\servicing\LCU before and after, you will see that the CU got unpacked there. When this happens, Windows updates will download the CU, say that it is installing it but will not require a reboot as all that happened was that the CU was downloaded and unpacked into the LCU folder.
I build 100s of ISOs myself per month, never had this occurring other then on some vbox installs. Iirc, this was already discussed.
It was and I was not the only one seeing this. I also do hundreds of installs but 0% are virtual. Other than my Windows 11 VM, all installs are on real hardware.
Nothing was changed, after installation, only .net was activate on the "live" machine before Windows update
That is the nr 1 reason, FOD changes causing the re-offering of the LCU, to update the changed components. When you don't want to have the LCU re-offered after installation pre-enable .netfx35 and integrate the LCU and NDP35-4xx CU afterwards.
Confirmed: Microsoft is apparently planning to launch Windows 10 version 22H2 in October and it’ll be called ‘Windows 10 October 2022 Update’. Microsoft Spokesman - No official blog post yet. Spoiler: W10 22H2 Windows 10 October 2022 Update (arrives) is an enablement package: Microsoft is no longer working on new features for Windows 10 and it’s technically under maintenance mode. As a result, Windows 10’s next ‘feature update’ would be a minor release.
You can but mixing them can cause problems, the ndp35-481 and dbx update should be safe to mix with the others.
Windows 10 , since 2019 has been a very good OS , if we talk about windows... previous versions were more buggy.
try the below code in power shell in windows 10 , it will give you list of all windows 10 version you have upgraded from with dates. $OS=@(Get-ChildItem -Path HKLM:\System\Setup\Source* | ForEach-Object {Get-ItemProperty -Path Registry::$_}; Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion') $OS | Select-Object ProductName, ReleaseID, CurrentBuild, @{Name='InstallDate'; Expression={[timezone]::CurrentTimeZone.ToLocalTime(([datetime]'1/1/1970').AddSeconds($_.InstallDate))}} | Sort-Object "InstallDate"
Just an observation but .2075 has been a bit more likely to fail than other CUs this year. This is the first time in a very long time that I have needed to do an in place upgrade to get a CU to install.
Hello, do you know where I can find this version? es-mx_windows_10_consumer_editions_version_21h2_updated_sep_2022_x64_dvd_59c7e90e.iso If you can help me I would be very grateful.