For that we need to use the ftp service on website hosted server and the provider should allow it. I'm using a free website builder with hosting with SSL which doesn't allow FTP to load the website or any files. Will explore other options.
Hello MSMG. I am new user here, and thank you for toolkit. Does anyone know why i get inetcpl error after audit mode oobe in IE11 W10Pro (only happens after oobe bare metal) The image is healty, no sfc errors or dism restore health issues i have integrated drivers, net 3.5, dx9, calc and whd update pack to 19042.572 I have removed apps according to ToolKitHelper package list so the image is still genuine, + Mediaplayer, Ciep, insiderhub and onedrive , the rest is done with powershell after the os is installed I Installed vlc 7zip and so on from ninite through IE11, then sysprep is saved with clonezilla to deploy. Everything works like a charm, but ie gets inetcpl side by side errors, clonezilla is set to expand the drive to full size. As far as i know, is dx9 and IE not related, ? or can it be and expand, integrate, or remove issue, any help is appreciated
As you can see in this post, the SFC is clean until Image cleanup is performed which will generate a ghost SFC, then on second run the SFC will come clean. The issue is with the CU.
SolitaireCollection, SoundRecorder, StickyNotes, Xbox.TCUI, XboxApp, XboxGameOverlay, XboxGamingOverlay, XboxIdentityProvider, XboxSpeechToTextOverlay, YourPhone, ZuneMusic, ZuneVideo I remove these apps with powershell from the image online and -allusers, when os is installed
I'm retired but still fix and build PCs so I need to know what is broken and how to fix it. My "just how old is too old to run the current OS" system is a rp5700 and it runs 20H2 without an issue. That thing is DDR2/Core 2 Duo era.
in General, you can not worry? And quietly delete components 19042.572? Or you need 19042.608 that the original sfc / scannow was clean. What do you recommend?
Nowadays FTP admitted as obsolete unsecure standard that will be excluded from the browsers soon (e.g. Firefox). But some providers (potentially) may reorganize FTP traffic transfer capabilities over HTTPS protocol. 1) I can download Packs from cloud.mail.ru over TOR. But UxTheme patch is likely absent. The rest 2 I wanted were downloaded successfully. (Now I understand this is not your cloud also; the shared repo has been provided by other user). 2) What could you recommend around Cleanup (before Apply changes) for LTSC (1809) ? Are present issues with CU & Cleanup affect on this older OS in the same way, or there are some differences? Well, at least suppose?
@MSMG Do you have a plan to try and get the Edge Chromium package removed in the next version? Is it something that's possible given how it is right now?
Found (answer by @MSMG): About UxTheme patch for LTSC and why it has beed removed Spoiler: If you update the system it will break the patch due to frequent changes in update.
Can you test just with the Toolkit removal and without any other packs integration or customization to make sure the removal is clean.
Ok, sure i will test ToolKitHelper package removeal only, on bare metal, to see if the issue still exsist, the strange thing is, it only happens when using oobe you will hear from me later.
It's not the browser thing, it is uploading the website files to your web server through a FTP/STFP client like Filezilla. UxTheme files get changed with each updates and also breaks the SFC scan so left it users choice to mod the file and integrate them to the image. Haven't tested cleanup thing breaking SFC for LTSC, 1809 or 1909 images, will test when I do get time later.
You can remove the Edge offline from Store ESD images, you can add the below command in setupcomplete.cmd file and copy it to <sources\$OEM$\$$\Setup\Scripts> folder to uninstall the Edge on first boot. For 32-bit Code: C:\Program Files\Microsoft\Edge\Application\83.0.478.58\Installer\setup.exe --uninstall --system-level --verbose-logging --force-uninstall For 64-bit Code: C:\Program Files (x86)\Microsoft\Edge\Application\83.0.478.58\Installer\setup.exe --uninstall --system-level --verbose-logging --force-uninstall Change 83.0.478.58 to the one included in the image.
You can use stable 19042.572 or preview 19042.608/610 but it's the source of image which should be clean to avoid SFC, if you don't worry SFC error then use any of the images with the these versions. Note: Next update will only support next patch Tuesday stable CU.