New
#810
With that file resource error I'll assume a file within the update didn't download correctly?
I have a question regarding this subject, how can I make a multiple index ISO with different SKUs?
When I upgrade I can see in SoftwareDownloads that apparently everything is there (the CAB files for Core, CoreSingleLanguage, Education, ENTERPRISE, ENTERPRISEN, Professional etc all exist). This script (and all others I tried) ignore this and only give the option to make an ISO or .wim of Pro.
Is it possible to make an ISO with all indexes included (same as if you create it from UUP downloaded direct from MS) or not?
EDIT: I want to do this as you can't upgrade the Pro wim index to ProfessionalWorkstation - it has to be Home, S or (perhaps, I've not tried it) Cloud SKU.
In any case it would be nice if we could make a multiple index ISO the same as MS supply.
Last edited by lx07; 23 Aug 2017 at 16:15. Reason: Reason...
Chrome will download the file - go to Chrome downloads from the Chrome settings control, and you will see something like this:
Select keep Dangerous file, then, keep anyway:
and the file is saved.
I think that S and Cloud are identical in the same way as Core and Home are.
The thing is that Microsoft are moving away from .WIM and .ISO as the method of software distribution.
Multipart WIMs with multiple images aren't the way forward - they don't fit on DVD disks any more, and when the common Windows 10 code base is fully Unified (as in Unified Update Protocol - UUP), all that is needed are the correct insertion of the product code for the required edition.
The installation base is the Core image, modified by the edition either of the digital license from the machine or previous installed version (genuineticket.xml), or of an upgrade product key, and there is some hierarchy, or even a branching structure to the upgrade path.
Microsoft has decided that CAB files can deliver the modification packages to change editions - in a similar way to language packs, that deliver a whole new language to the OS, whole new policy and feature sets may be unlocked, without re-installation. Featuresets may also be removed for 'N' versions
And the whole shebang is serviced via DISM, or more correctly by the Component Based Servicing API, of which DISM is a commandline tool.
It is not really new - the Windows 7 anytime upgrade service was the forerunner of this. Somewhere, in Windows 10, there is a STARTER edition lurking!
***********************************
One change to the files in the C:\Windows.old\WINDOWS\SoftwareDistribution\Download\0fa23944c6eb2bd5f7585f5c6806b5b5 folder (or whatever you have as the download folder that is found by searching for Ext:ESD file location) is that at some time before 100% of the install is complete, most of the larger ESDs, CABs, and folders get removed leaving what remains in the Windows.old path after install.
Apparently this change makes it easier for installs on limited storage to complete successfully.
This means that if you leave it too late, UUPtoISO may find that some of the files it depends on may be removed before they have been processed into WIMs.
Along with the quicker install times noted (for some users!) you may need to be snappy when deploying UUPtoISO!
There is possibly some optimum % of download complete to start UUPtoISO, as after installation starts, there may not be enough time to process all the UUP download files to Install.WIM.
This of course will vary with machines constructed with SSDs or HDDs, faster or slower processors, or greater or lesser quantities of RAM etc.
Last edited by Fafhrd; 24 Aug 2017 at 00:53.
Just as I figured. My UUP upgrade files were not complete and/or corrupted. After update was complete, I performed a store repair with DISM then an sfc scan. Here are the results. Right after reboot command there was a short "Working on updates" window and rebooted. No way to back out of the update once started, yes? Is it worth rolling back and starting over?
Microsoft Windows [Version 10.0.16273.1000]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.16273.1000
Image Version: 10.0.16273.1000
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
The system file repair changes will take effect after the next reboot.