[DISCUSSION] Windows 10 Final Build 19041/2/3 (PC) [20H1/2 / 21H1 vb_release]

No problem.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

has anybody tested UASP storage Driver issue in this release of Win10 19041.x.

to fix we have to manualy copy uaspstor.sys & usbstor.sys from system32/drivers directory on 18362/63 system & paste it to same directory on 19041.x system.

 

that's odd and unlikely

 

You need to login to view this posts content.

 

so, it's been more than 1.5 days & 44hrs+ & still nothing, no update for 20H1

 

How did you solve that? In one of my system, I ended up installing that KB manually after downloading from MCU website, in another system (of mine), that installed flawlessly. Still, 3 systems left, will see that.

 

Drives like a crazy.
20H1 got COVID-19.
Hey, Maybe M$ want to cancel this build and move to something like 19042?
Could not wait more. Decided to raise my hands/voice...

 

New build could make new bugs. So it's better to add CU to 19041 (Fix bugs in the same build).

 

You're completely right. Agree.
I upgraded many PCs/laptops here.

 

New CU also can create new bugs whether it's newly compiled into a new major build iso or by dism'ing it in.

19041 = 20H1 and will be 20H1, it's still SLOW ring, so updates can appear whenever they are ready to be released.

 

About the ISO, you mean ISO from MS or ISO from esd ?

 

From time to time i have troubles following your thoughts.

There will be no new major new build for 20H1, only follow up updates for the current 19041.xxx release.

I responded to this:

It's nonsense, to be short.

 

I know that "There will be no new major new build for 20H1".

I didn't talk about upgrading.

 

I think I found one possible source of the safe_boot upgrade issues. I tried to use some USB gadget (and tried to re-install it's software package to get the driver installed because I purged all stale drivers earlier) and got a blue screen of death blaming aksfridge.sys, Windows couldn't boot until I removed the corresponding driver with Driver Store Explorer. It was called some 'SafetyNet' something. Goggle says it's some kind of DRM solution which makes some sense in terms of incompatibility (many Win10 updates cause issues with DRM solutions) but not much sense in relations with the driver and software I tried to install. I could grab a driver-only package from the manufacturer (instead of the whole software+driver bundle) and managed to use the USB device with another software (no more BSOD), so I guess this is a 'software extension driver' (not a real device driver but appears as such) and probably was part of the software which doesn't need license keys other than the hardware keys in the USB devices but I guess they use this "Aladdin HASP" DRM thingy for that. I think I already had issues with this Aladdin thing in the past. It has a strange name and I loosely recall googling around for it some years ago (and being similarly surprised what kind of DRM solution this could be and where it might belongs, why it's even installed on my system...).

 

You need to login to view this posts content.

 

It's important to note that Seattle is in a lockdown because of COVID-19. While Microsoft employees probably can do a lot of work from home, it's hard to believe there won't be some impact on development and testing.

 

You need to login to view this posts content.