Windows 10 Hotfix Repository

Yes you can apply delta esd directly to partition

Code:

wimlib-imagex apply Cloud_en-us.esd 3 Z: --ref=*.esd

but the cab>esd step is required
dism/imagex/wimlib all require reference files to be wim/esd, cab files are not recognized

not sure how Microsoft creates the upgrade os without this step

 

A cumulative update to be released today I think?

I checked the Microsoft Update Catalog, it hasn't been issued yet.

 

Patch tuesday is September 12th.

 

We only got 1 CU in Aug. We were suppose to get 2. So we could still get the 2nd Aug. CU at any time.

 

There a lot of office 2016 updates released today, still no CU.

 

Is there any equivalent command for dism that does the same?

 

Code:

DISM /Apply-Image /ImageFile:Cloud_en-us.esd /Index:3 /ApplyDir:Z: /SWMFile:*.esd

didn't test it though

 

that only happens when is really needed, no always and not each month.

CU is for September 12.

 

You need to login to view this posts content.

 

That did it with the /SWMFile: switch. Thanks abbodi.

 

You need to login to view this posts content.

 

yeah and lately since august and before more bugs cropping up and some huge bugs like august cu wiping out many win 10 and server 2016 history of updates list or log among others they need more insider/internal testing on cu's

 

You need to login to view this posts content.

 

The 1st CU is for Security Updates. The 2nd CU is for Non-Security Updates for each Month.

 

yep really although I think that Windows 10 is one fantastic O.S. but dash with little detail is always beta O.S. therefore I downgrade to W8.1 untill 2023 O.S. stable, reliable, faster why? because this O.S. is consolidate only get little updates for fix something and security also for me is clear as water imo

 

MS cannot even fullfill FCU before its release with all announced features.

No wonder they can't do stuff such another useless update.

 

I take a more liberal approach - I consider builds 15063+ to be sort of kind of like "RC" builds, especially now that MS officially stated that "Creator's Update is ready for business deployment", but the actual stable version of Windows 10 is 14393 because that is the build MS chose to use for its LTSB branch. I mean 15063 was released with a corrupt component store (DISM ScanHealth/Repair was not fixable until 15063.332 or something like that) - you just don't do that in/for a stable OS release...It was literally - experimental release.

I do so much testing and image editing with NTLite that I have several Acronis backups of 14393.1670 and 15063.540. I don't think I ever want to install a non-NTLited/non-edited/bloated version of Windows 10 ever again. Once you get a glimpse of what Windows 10 could've been like without all the bloatware, you'll never want to install a full version of any Windows 10 branch/release/build.

I use 15063.540 for gaming and every day tasks ever since CU 540 came out, which is about the time MS stated that 15063 is ready for business deployment. 15063.540 has some HyperThreading optimizations when it comes to some processes/services, utilizes FullScreen Optimization in games, has slightly better RAM management, supports WDDM 2.2 (not that I am into virtual reality, which is the real purpose of WDDM 2.2), and also has MTP USB improvements that can be of benefit to those who frequently transfer data/files to their mobile phones. It sucks that the cost of having these few useful optimizations is having to install a super-bloated build of Windows 10 with its revenue-generating Store, but NTLite or at least MSMG Toolkit can really help with that and they are the only reason I actually installed and use 15063.

 

Is there such a thing as TRUE ResetBase? Some say that when you rebase normally, it does not rebase FULLY, but delta-packages older\superseded updates\files. If I enable the TRUE rebase on a stock Windows 10 image, save that image with that one single change, run W10UI with updates (NOT including NetFX 3.5), then would W10UI's final rebasing would TRUE rebasing, where no delta-packaging takes place and the whole image is fully rebased? Or is there a special command for that? What about other files, like boot.wim and winre.wim - do they also support delta-packaging and need something special to have a full rebase?

 

How do I edit the image's Service Pack info? For example, the latest 15063.483 official Pro VL image refresh has Service Pack version 296 and I want to change it to 540 and can't figure out how. I tried WIMLib, but did not succeed...

 

I can confirm now that there is a setting that allows for a full ResetBase, which rebases the OS without packaging any old data. If you apply a full rebase you no longer get any WinSxS Temp file build ups, no pending operations, no matter how many times you rebase or use DISM ScanHealth or SFC ScanNow - it stays empty and it also saved me a bunch of space on my wim - about 200MB.

I think this was discussed in MSMG Toolkit thread, but I am not sure as that discussion involved NetFX 3.5 pending flag. I hope Aboddi introduces enabling of full ResetBase into his next W10UI release. I think its an old setting that not many people knew about... Or maybe its new? I definitely like it and approve its use .

I wonder why MS keeps full ResetBase disabled. Partial rebase is still permanent AFAIK and unless you can get your pre-CU component store data from those compressed delta packages, there is no point in keeping full ResetBase disabled. Incomplete rebasing forces OS to do some constant cleaning too, wasting good CPU cycles!