Looking at the missing performance data in Task-manager>Startup got me thinking what the Kernel Boot Operation would show and event viewer has a lot of errors.
Same with WMI Activity>Operation logs
Edit: I am seeing the same errors in a 2004 VM so it not new on event viewer errors
Last edited by EdKiefer; 22 Oct 2020 at 07:55.
I installed version 20h2 with the Enablement Package Feature Update to Windows 10 version 20H2 and have no issues with the task manager in the Startup tab.
I did some tests, the Startup tab refreshes well with new entries (apps enabled on startup) and the ones that remain in this tab, they are enabled or disabled.
edit: running now is empty but I don't care.
your computer uses Conexant audio drivers, catspyjamas?
you need to update the audio drivers, not upgrade to either 2004 or 20H2.
check with the PC manufacturer of your computer if they have posted new Conexant drivers
Synaptics (who acquired Conexant Systems Inc.) is relatively slow in releasing new Conexant audio drivers to OEMs that are 2004/20H2 compatible
Yay - a way to run Legacy Edge assuming it is still installed
Delete BrowserReplacement key at
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}
Obviously do this at your peril (make image back recommended)
Ugh. me too. Not newly installed either. I count on exclusions seeing as MS won't let me turn off scheduled quick scans.
How can MS f up such basic stuff and release it?
EDIT: Worked around this by using group policy editor to exclude paths (then they also show up in the defender exclusion list).
Last edited by Geneo; 22 Oct 2020 at 13:08.
One of them yes. It contains a single file that is not compatible as per the known issues in 2004 and 20H2. I've had the your machine not ready etc banner blocking the update in my WU since MS released 2004, so I'm perfectly aware I can't update and need to remain on 1909.
I think pigs will fly before HP release an a new audio driver for this computer (it's 4yrs old and doesn't receive driver update anymore from HP, and wasn't even on the HP list of machines tested for compatibility with 2004) and given that the issue has been marked as open since May 27th with MS (but reported to MS by insiders many months before this) - I'm thinking pigs might fly before MS/Synaptics release a fix either.
Just have to wait... The affected 2 in 1 is an outstanding wee machine and in spite of it's age, looks and performs as new. So I'll be gutted if 1909 is the last update I can do and support is withdrawn from MS in May 2021.
Surely the whole point of MS developing the New Edge was to be a replacement for Legacy Edge? There has to come a point where MS will no longer include any Legacy Edge code in the install media. As I understand it that point will be in 21H1. For now 20H2 seems to be an interim step, Legacy Edge code is still there but hidden from use, just as it is hidden when you installed Chromium Stable with the standalone installer.
For me it is a non-issue. The original Edge was widely panned from the beginning as being a 'feature-free zone'. Hardly anyone liked or used it.
Microsoft is building a Chromium-powered web browser that will replace Edge on Windows 10 | Windows CentralMicrosoft's Edge web browser has seen little success since its debut on Windows 10 in 2015. ... it launched with a plethora of issues that resulted in users rejecting it early on. Edge has since struggled to gain traction, thanks to its continued instability and lack of mindshare, from users and web developers.
2) You cannot directly do a repair upgrade and keep anything. There is a workaround i.e. you have to remove the enablement update from old program and features menus. It is not shown in windows updates.
Now that is a seriously bad issue which I have just tested and confirmed.
There seems to be a bug in its version comparison algorithm. It's perhaps understandable how this bug came about. the 20H2 install media is all the code for 19041 with the enablement package to raise that to 19042 included. Setup seems unable to understand that it can indeed upgrade an installed 19042 to it's 19041+enablement build and keep the installed programs.
It's an unforgivable error on MS's part. The same potential for a mix-up was there for the 1909 install media. I've also tested an in-place upgrade of a 1909 machine with a 1909 ISO and that one does allow you to keep installed programs - so it should be possible with the 20H1 media too.
Last edited by Bree; 22 Oct 2020 at 22:36.
Yet another example of lousy software engineering by MSSurely the whole point of MS developing the New Edge was to be a replacement for Legacy Edge? There has to come a point where MS will no longer include any Legacy Edge code in the install media. As I understand it that point will be in 21H1. For now 20H2 seems to be an interim step, Legacy Edge code is still there but hidden from use, just as it is hidden when you installed Chromium Stable with the standalone installer.
For me it is a non-issue. The original Edge was widely panned from the beginning as being a 'feature-free zone'. Hardly anyone liked or used it.
Microsoft is building a Chromium-powered web browser that will replace Edge on Windows 10 | Windows Central
Now that is a seriously bad issue which I have just tested and confirmed.
There seems to be a bug in its version comparison algorithm. It's perhaps understandable how this bug came about. the 20H2 install media is all the code for 19041 with the enablement package to raise that to 19042 included. Setup seems unable to understand that it can indeed upgrade an installed 19042 to it's 19041+enablement build and keep the installed programs.
It's an unforgivable error on MS's part. The same potential for a mix-up was there for the 1909 install media. I've also tested an in-place upgrade of a 1909 machine with a 1909 ISO and that one does allow you to keep installed programs - so it should be possible with the 20H1 media too.
Quote
