[DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release]

mistake in typing

19042.661 i was wrong.

 

You need to login to view this posts content.

 

Well I know about the dates and such, and I have been upgrading 1507 - 1609 - 1803 - 1809 - 1909.

I feel 1909 is very stable, again would I gain anything from updating to 20H2 at the moment or should I wait til next year?

Also, feature wise, have it changed drastically?

I want your honest opinion if I should update or hold off a little while longer.

 

Thank you for a sincere answer, I think I will continue to use 1909 a little while longer but I have downloaded 20H2 just in case.

I have always felt that the fall releases of new Windows 10 updates have been more stable and mature in general.

20H2 shouldn't cause trouble on a i7 8700K right?

 

even on i5-3450 i am using 2004 20H1 build working fine at my end as vm.

 

20H2 is also called the October 2020 Update, a Fall release.

 

hopefully not a dumb question OK here it goes in Microsoft store why does it remember your old apps you previously installed when you never signed in a Microsoft account I must installed fresh builds 50 times now and always there ready to install...

 

whatismyip; whatismysubnet; whatismyhwid;

 

whoa going to Linux

 

that is old

 

One of my test systems is a rp5700. That thing is ancient but with a SSD is actually runs pretty great on 20H2.

 

I just did a fresh install last night on an ancient Dell XPS M1210. It came with Vista originally, has 4 gigs of ram (but for some reason it will not allow the use of more than 3.25). I installed an old 120 gig SSD that I had laying around, and loaded the most recent 19042.630 Windows 10 Pro (from uupdump). The only real problem was the video driver. This has an Nvidia GeForce Go 7200, and there are no Windows 10 driver. Google searches led me to several older Nvidia releases (309, then 307, finally 179). That last one did the trick.

I think I may wipe the drive and try a light version of Linux, just for grins.

 

Which windows architecture did you install ? 32 or 64 bit ?
windows 32 bit versions handle only 3 Go of ram so if you installed 32 bit version with 4 GB ram, that's normal that only 3,25 re recognized so you need to install 64 bit to hopefully get the entire ram recognized.

If it's 64bit version that is installed, you may need to update the bios to hopefully get this issue fixed but with no garantie that the problem will be solved after that (it worked for some people and didn't work dor others) by taking into account that the flash of the bios can be fatal if you get the wrong bios or if a power cut occurs during the flash procedure so it's at your own risk.

 

You need to login to view this posts content.

 

@SM03
KB4023057 is delivered exclusively via UUP for 1809 and later
and as unifiedinstaller.exe + UpdHealthTools.cab (UpdHealthTools.msi)

even in 1803 and earlier, Windows10.0-KB4023057-x64.cab = Windows10.0-KB4023057-x64.msi

 

19042.661 brings Microsoft meet now in task bar next took clock