Though he has included Image cleanup in this steps, I don't know whether he really did it or not coz the Image cleanup breaks SFC with updates.
Does that mean don't do the cleanup on this step? [L] - Apply & Save Changes to Source Images using [Apply->Apply & Save Changes to Source Images] menu.
Good evening. Using version 10.8 with ISO 20H2-Build 19042.572 I have removed the apps, which have been regularly deleted, but by checking for corrupt files (sfc / scannow) I have found corrupt files. This is the log file report. Code: 2020-11-05 22:54:53, Info CBS Starting TiWorker initialization. 2020-11-05 22:54:53, Info CBS Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2 2020-11-05 22:54:53, Info CBS Ending TiWorker initialization. 2020-11-05 22:54:53, Info CBS Starting the TiWorker main loop. 2020-11-05 22:54:53, Info CBS TiWorker starts successfully. 2020-11-05 22:54:53, Info CBS Lock: New lock added: CCbsWorker, level: 5, total lock:3 2020-11-05 22:54:53, Info CBS InitializeUpdateReserves called 2020-11-05 22:56:53, Info CBS CbsCoreStopIdleProcessing is not implemented. [HRESULT = 0x80004001 - E_NOTIMPL] 2020-11-05 22:56:53, Info CBS TiWorker signaled for shutdown, going to exit. 2020-11-05 22:56:53, Info CBS Deleting the contents of directory: \\?\C:\Windows\CbsTemp 2020-11-05 22:56:53, Info CBS Deletion of: \\?\C:\Windows\CbsTemp successful 2020-11-05 22:56:53, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3 2020-11-05 22:56:53, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2 2020-11-05 22:56:53, Info CBS Ending the TiWorker main loop. 2020-11-05 22:56:53, Info CBS Starting TiWorker finalization. 2020-11-05 22:56:53, Info CBS Trusted Installer core was not initialized. 2020-11-05 22:56:53, Info CBS Ending TiWorker finalization. Some idea? Thanks
@MSMG I always wanted to ask you, exactly in which case I should use mounting Setup Boot Image and/or Recovery Image? Code: Do you want to mount Windows Setup Boot Image ? ['Y'es/'N'o] : Do you want to mount Windows Recovery Image ? ['Y'es/'N'o] : Then I will know should I report a bug or not.
How can I recognize such updates? (Sorry for my stupid question). Also, as I can see in the message above: ...what else? I just want to understand better the cases I must press [Y] to make job properly.
Well, I often thinking that MSMG need a good HELP with short descriptions for options (and more extended points for more complicated things). Or @MSMG will continue to answer on the same questions again and again for every new user (like me also) which want to learn the MSMG bundle and main ISO tricks. The present README is not enough (I agree it useful also to understand the main workflow for different OS).
yes I totally agree and I always think about it since the first Toolkit even in Windows 8.1 times so I believe that we should collaborate with our master in other parts of the Toolkit itself a good example is the readme as you said in my view the our master as a programmer knows how I’ve never seen doing his job the best possible before but the Readme needs to improve to be more objective we’re going to combine our thinking and improve the Readme what you think friend ...
I think, the better way is leaving README as it is (as a Main workflow for different OS) and create a separate HELP file with the next stucture: Code: • Option 1 Description • Option 2 Description The main issue is a time (as usual) for such big, accurate and detailed work... (I have my own draft on my native language. Also I'm not "an English man in NewYork" (C), as well)
If you are integrating features like Drivers, Language Packs, DaRT, Updates to boot.wim and winre.wim then you need to mount them.
From Updates description provided by MS site or open the update file with 7-zip and open the package xml file to know to if the update is applicable to WinPE images.