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

Anyone have information for Windows 10 IoT 1903 ?

 

Hi, I've a lot of difficulties upgrading my current Windows 10 build (18363.327) to 329 version.

I've tried via DISM command and it returns an error.

If I try uupdump to create ISO and run setup.exe it does not allow me to keep programs saying maybe I'm trying
to install an older Windows 10 version and thus I can't update it in this way too.

Is there anyone experiencing same issues around ?

 

please separate threads 18362.xxx and 18363.xxx

 

You need to login to view this posts content.

 

I can't see your image file but I've 0x800f081f error using DISM, while if I compile ISO it says it can't upgrade it as I'm trying to install an older Windows version.

 

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.

 

You need to login to view this posts content.

 

Sorry, but can somebody help me?

May Storage Sense delete somes files and folders I don't want it to like the ones from the Documents folder (like if it was selected as Edge's download folder or something like that)?

How can I recover Chrome's jumplist? I lost "New window" and "New incognito window", I don't know why (if must be a Windows setting or program removing it since I'm always losing it after installing Chrome for the first time).

Also, if I disable all notifications on the Notifications tab on the Settings app and not disable the ones from Focus Assist (if these are notifications at all, I don't know) as well as not disable it (Focus Assist) may I have any kind of notifications on the Action Center (and maybe in other places)?

 

@Schroedinger2015 yes, they removed some components in .329, and also .327 had a corrupt component
I will post a fix in a few hours

 

no, they are different types of faults
Most of the time problems occur because new update reverts components back to .1 — I guess this happens because they're built from a different branch
The only two actually corrupt updates i noticed were
.10013 (amd64_microsoft-windows-c..cal.desktop.cortana had a corrupt reverse delta bc it had less files than .1 version of same components)
.327 (amd64_hyperv-compute-guestcomputeservice component is incorrectly marked as new instead of updated — and that's on top of the trouble with .329 reverting some components back to .1)
In short, the new forward-reverse delta system generates more trouble than it's worth. “Agile” development at its finest.

IIRC they have solved the .263 problem in later updates by re-adding the relevant component. I think solving .10013 and .327 requires either a servicing stack/WU update or a change in how the updates are built bc the process does not know the old update has bugs

That's to say, i haven't noticed these problems in any public updates, only RP ones

 

I'll be waiting for your fix.

I tried the one you posted in the other thread and I assume is not for 18363 but for 18362.

 

IDK why you can't see the image in my post but just to let you know, it's the same error that am getting too.