[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

>>> Immaturely <<<



You are on ignore, child

 

Happy Independence Day (Malawi)!

 

my notification center open but doesnt work
can tell me WHY?

 

what exactly is not working?

 

I gave up on 1903 after all of the bugs. It's been about two months. Are there improved builds that fix some of the major problems?

 

Try 19H2 (1909)

https://forums.mydigitallife.net/th...19h2-pc-slow-19h1_release_svc_19h2_rel.79895/

 

that most likely to be more buggy than 19H1

 

It's not. It's exactly the same as 18362.207.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Different CU states are delivered and offered via UUP, similiar to Windows update offers in general.

 

Please can you confirm or infirm the existence of my problem for those who uses 18362.207.
my problem is:
any 32 bits app when launched high rocket the cpu usage (10% or higher) , consequently I have
to wait a long long time before the app starts and shows its windows.

 

10% CPU usage loading an app is not high

 

32-bit applications have persistent problems on Windows 10.

 

I agree with your statement , as 90% of cpu usage is still available. but in reality the app windows do not show up for minutes
and if I start in parallel other 32bits apps then I see my cpu usage go up to 40%. my PC become non responsive.
For clarification : my post is not a critique about the version, only looking for solutions as I am a Microsoft fan since years and years

 

Solution: Use real applications (Win32) instead of UWP rubbish

 

I will track the apps I am using , if they are Universal Windows Platforms (UWP) apps.
the problem happens to Adobe acrobat dc 32bits too when launched. It seems that this morning
Adobe acrobat is more responsive. I updated in the meantime my bios (Asus Maximus X Formula)
plus the chipset drivers.

 

When will the esd of 18362.207 be released? No rush coz I'm downloading it via uupdump. Just curious.

 

You need to login to view this posts content.

 

Test if problem appears on a fresh install (not an upgrade). If not ... the upgrade is faulty .