@graver.x Did you tried to launch sfc /verifyonly two times? Please, check what's goin on at the 2-nd attempt (it may appear healthy, i.e. 1-st attempt may be false-positive).
@graver.x I'm not an expert and not sure about other issues in CBS.log, but have one advise for you (and everybody here) - do not remove 2 dependent packages responsible for making Restore Point: • SystemRestore • WindowsBackup 1) Making Restore Points while you use OS long time - isn't a great option to be safe and always have solid working configuration saved (by you manually or/and by system automatically)? 2) One of your issues (according to CBS.log) - is (missing) srclient.dll - Microsoft® Windows System Restore Client Library. So system would not able to fix some issues (if any and if you accept such method, of course).
@MSMG has already said that this current version will work with 19042.572. I admit that this information isn't the easiest to find Like you I do not want to be working with preview update and installing them. I aim to recreate my image on the second Tuesday of each month, which is usually when Microsoft release stable updates.
@Feartamixg - I now for 100% everything you mention. That were arguments only for @Enthousiast I have a question to you. Do you have Edge installed anyway in build 572 and MSMG v10.7 (if you actually had wanted to remove Edge)?
Yes, Edge Chromium remains installed. Although I do not use it, I would rather keep it as a backup browser - ie: for when I suspect a website might not be working in Firefox (rare).
@Feartamixg I see... Remaining the Edge was your decision. Not exactly what I wanted to know. Thanks, anyway.
What is it you want to know? I can perhaps test removing Edge Chromium tomorrow, if you wish? Which image, x86 or x64?
Don't worry, please. Someone who have build 508 installed can confirm whether Edge still there or not (when it should be removed over lists).
I'll try that, though I have deleted that package from the offline image and also deleted the WinSxS folder (and I have removed Windows Update) and Edge still installs... oh no, more tests, more headaches. Waiting for MSMG to save us from hell LOL
I have made a 2 tests with 2 Enterprise builds : 572 & 608 - both installations FAILED with same HW configuration error during setup. NEVER had such error. I see this 1-st time in my life. Both images were based on one ESD build 572 (official MS delivery) and converted to ISO. Build 572 - without integating updates. Build 608 - with one KB update. No errors during the whole process: download, convert, mount, update, edit, rebuild, etc... This is the first time I've used ESD. Before I always used to ISO only. Now my test machine have no OS and I need to install stock build first... "Have a look under the cap, and have a try again" (C). Just wonderful.
hmm there really is something wrong, here the other day it happened to me also during the installation the system stated that my hardware was not compatible !! and restarted alone so I put the pendrive with LTSC and I am running now without problems this way I am running these new versions of Windows I will stay with LTSC as long as possible
ingviowarr, You may be right in your assumption that removing these two components can lead to sfc problems. But since we are not experts, we will wait for MSMG's response. I hope the result of my test will be useful for improving the Toolkit. Creating restore points has long been a useless option for me. Therefore, since the Toolkit allows you to do this, I would like to remove these components as well. Acronis_WinPE.iso + Shadow Defender = (for my experience) - the best tools to ensure the safety of my OS. In addition, as far as I understand, reading the forum, such a problem should not arise with EN_US images. Therefore, I assumed that the sfc errors are still related to the remaining resource files. I hope MSMG will soon dispel our doubts
My humble opinion - and this option is not excluded. By the way, I came across the fact that for a mysterious reason for me the script uup.rg-adguard.net, used on my PC, does not work properly, giving errors of integration of updates, etc... in contrast to it, the script uup.dump.ml creates images in the best possible way, without errors.
Yes checked with Step 2-1,2-2 the ESD-WIM feature is broken fixing it now, it will be available in next version.