For what? Just install abo's package first. It#s not like that MSMG is the only app in the world who need those damn dll's, right?!
Is there a way to apply a custom theme from registry replacing the default Aero (making it permanent and default for all new users) without having to use firstlogon.cmd ?
Yeah! happens with Windows defender too. KB4525252 is the latest preview of monthly rollup and has added new location modules and location telemetry. If @MSMG likes, we can really narrow it down to 20 update packages to pin point which one is really causing it. But based on the tests done by our esteemed friend @AeonX, apparently it's KB4525252 package what's causing the issue. I'll wait for the updated version of the toolkit. Hopefully it rolls out before 10th of December, that's when this months rollup will be due from Microsoft. I'll grab the new rollup package and updated version of the toolkit and start with a fresh untouched store ESD. Thanks for the input @AeonX, highly appreciated.
Yesterday I got mismatch in following, I also given new SHA-1 for these files Mismatched List 42e0473be29b46b0a1ce7f4d5419143a0ffab559,Packs\Apps\GettingApps.txt b0614a0489e3ba02b1ff1db06f40179a4f63455f,Packs\EdgeBrowser\10.0.18362\Microsoft-Windows-Internet-Browser-Package~31bf3856ad364e35~amd64~~10.0.18362.1.cab 4c7de8bc4b28cd9f0a18425c63dabd81ced1a432,Packs\EdgeBrowser\10.0.18362\Microsoft-Windows-Internet-Browser-Package~31bf3856ad364e35~amd64~en-US~10.0.18362.1.cab 35f8226e86aa0958da6e0a87cfd702fc2e618536,Packs\EdgeBrowser\10.0.18362\Microsoft-Windows-Internet-Browser-Package~31bf3856ad364e35~x86~~10.0.18362.1.cab 375340e79dac52f4a50750fc11d469870c4420cc,Packs\EdgeBrowser\10.0.18362\Microsoft-Windows-Internet-Browser-Package~31bf3856ad364e35~x86~en-US~10.0.18362.1.cab 5f8e632d027eeab65d3ffcaf7ca5daaef0d0b9b3,Packs\NetFX48\w7\NetFX48.tpk 63852c3a44bf2e4bc47a6f5122543c506de60166,Packs\NetFX48\w7\NetFX48_x64.reg 611a0cf17152199e3142c3431937a77d815575b1,Packs\NetFX48\w7\NetFX48_x86.reg 9978ed76f92400e386228d1d8a8a3eadfe665844,Packs\NetFX48\w81\Microsoft-Windows-NetFX48-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.cab 7c6ac1b9cf7e5f2b2b453b98b18578f6a0eee4a2,Packs\NetFX48\w81\Microsoft-Windows-NetFX48-Package~31bf3856ad364e35~x86~~6.3.9600.16384.cab 161bc0117fb1243109f74369fa2d6c6954283605,Packs\WSL\10.0.18362\Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~~10.0.18362.1.cab c0a781398ad1c25801f8b7e3bdda3d1704b2ffdd,Packs\WSL\10.0.18362\Microsoft-Windows-Lxss-Optional-Package~31bf3856ad364e35~amd64~en-US~10.0.18362.1.cab Files are present in Packs folder tree but not in SHA-1 7aabe41baab195e985af962b7c4aeca77e3116c7,Packs\Apps\w10\10.0.18362\Microsoft.NET.Native.Framework.2.1_2.1.27427.0_arm__8wekyb3d8bbwe.Appx fb8b4e41071c18d1fee8e04bbd20706b1758726d,Packs\Apps\w10\10.0.18362\Microsoft.NET.Native.Framework.2.1_2.1.27427.0_x64__8wekyb3d8bbwe.Appx b93d2409131e7413e8860fb1879b60125068e7fe,Packs\Apps\w10\10.0.18362\Microsoft.NET.Native.Framework.2.1_2.1.27427.0_x86__8wekyb3d8bbwe.Appx 72940e3e896ebcb8312ebe57b7a3b58f5e7f5128,Packs\Apps\w10\10.0.18362\Microsoft.NET.Native.Runtime.2.1_2.1.26424.0_arm__8wekyb3d8bbwe.Appx bae43a214116ab8ad7c99374d769b1b4702577c7,Packs\Apps\w10\10.0.18362\Microsoft.NET.Native.Runtime.2.1_2.1.26424.0_x64__8wekyb3d8bbwe.Appx 35fe9d6696a985430525367f67281418f21aa7ae,Packs\Apps\w10\10.0.18362\Microsoft.NET.Native.Runtime.2.1_2.1.26424.0_x86__8wekyb3d8bbwe.Appx f8e9c40c1ef2391f01abec684a90cbe548f9ac2c,Packs\Apps\w10\10.0.18362\Microsoft.UI.Xaml.2.0_2.1810.18004.0_arm__8wekyb3d8bbwe.Appx a9fe50a2feb53f938e6dcd802f8304ccdb9247a0,Packs\Apps\w10\10.0.18362\Microsoft.UI.Xaml.2.0_2.1810.18004.0_arm64__8wekyb3d8bbwe.Appx 784246407dd5ebe49a6986b6cc2b9e83effab74e,Packs\Apps\w10\10.0.18362\Microsoft.UI.Xaml.2.0_2.1810.18004.0_x64__8wekyb3d8bbwe.Appx 174f3fdfd2cbf510cfecae81891c15716dc6d8bf,Packs\Apps\w10\10.0.18362\Microsoft.UI.Xaml.2.0_2.1810.18004.0_x86__8wekyb3d8bbwe.Appx Files referenced in SHA-1 but not in Packs folder tree adb5ac19d0be21ec2cb0f08776fe65ef86f97651,Packs\Apps\w81\Microsoft.HelpAndTips_2014.1204.1.4543_neutral___8wekyb3d8bbwe.AppxBundle 731727383054f63df680d81d516b22a9909dc1a2,Packs\LanguagePacks\w7\x64\renlp.cmd File Names referenced in SHA-1 differes from File Names in Packs Folder Tree 76fcdcfa61752a9dc04f1465977d7142e8ba3911,Packs\NetFX35\w81\x64.7z 9a957e09c15158b0a8c988812857e8f1d14f9a2c,Packs\NetFX35\w81\x86.7z File name Should be LanguagePack rather than Language-Pack Packs\LanguagePacks\w10\10.0.17763\x64\en-GB\Microsoft-Windows-Server-Language-Pack-Package~31bf3856ad364e35~amd64~en-GB~10.0.17763.1.cab
May be you are using the old SHA-1.txt, do check the latest one uploaded on 9th Nov which has the correct hashes. Will correct the Microsoft.HelpAndTips_2014.1204.1.4543_neutral___8wekyb3d8bbwe.AppxBundle and renlp.cmd
@MSMG I tend to plan Windows servicing for mine, friends and family PCs a long way out. I had originally planned to move all PCs to 1909 in January/February 2020. The last thing I want to do is come across pushy, so please don't take this out of context. I'm just trying to plan how I am going to service and support 20 odd PCs that are all still running 1809. Do you think the "removed components get restored" issue is resolvable, and a viable solution for future editions could be implemented? This is Microsoft's servicing life cycle. So I need to decide what I am going to do with the 10 Pro PCs I am currently supporting. As you can see, 1809 Pro runs out of support in May next year. Code: By Windows 10 version, below are the availability and end of service dates segmented by edition. Windows 10 version history Date of availability End of service for Home, Pro, Pro Education, and Pro for Workstations editions End of service for Enterprise and Education editions Windows 10, version 1909 November 12, 2019 May 11, 2021 May 10, 2022** Windows 10, version 1903 May 21, 2019 December 8, 2020 December 8, 2020 Windows 10, version 1809 November 13, 2018 May 12, 2020 May 11, 2021** Windows 10, version 1803 April 30, 2018 November 12, 2019 November 10, 2020 Windows 10, version 1709 October 17, 2017 April 9, 2019 April 14, 2020 Windows 10, version 1703 April 5, 2017* October 9, 2018 October 8, 2019 Windows 10, version 1607 August 2, 2016 April 10, 2018 April 9, 2019 Windows 10, version 1511 November 10, 2015 October 10, 2017 October 10, 2017 Windows 10, released July 2015 (version 1507) July 29, 2015 May 9, 2017 May 9, 2017 * Windows 10, version 1703 for Enterprise, Education, and IOT Enterprise editions were released on April 11, 2017. ** Serviced for 30 months from release date per September 6, 2018. Again, I know you are currently under a lot of pressure with several issues, and I'm just querying if the issue is fixable. If not, I'll have to look at alternatives.
Yes I can understand the issue with components returning, there are two states where the Windows Update fails partially and the other one where the components do turn, I need to experiment to get a intermediate state where both the WU should work and the components shouldn't return. Been busy with a lot of issues and it's taking more time, I do advise you to move to LTSC 2019 if you want to keep v1809 and once there's a fix for v1903/1909 then do the switchover. Do wait for the next release to get fixes for v1809/v1909 and then switch to LTSC 2019.
Hitting a snag . . . Trying to build iso with v. 1809 (17763.1) I am using ToolKit v.9.5. According to the Readme, the order of operations is different than in ToolKit v.9.4. In 9.4, the order or operations is: Integrate the required Windows Features Remove all required Windows Components Integrate Windows Updates (using WHD) In ToolKit v.9.5 the order of operations is: Integrate the required Windows Features Integrate Windows Updates Remove all required Windows Components I have successfully completed the process using 9.4. Now I am making another iso using 9.5, steps shown below. The process will not complete. When I get to Windows component removal, I get a message shown in step 4 below. 1. [A] Selected source image with no problems 2. [D] Integrated required Windows features with no problems 3. [E] Integrated Windows updates using WHD with no problems. Selected option 4 for: Windows Setup Boot, Install & Recovery Images 4. [G] Remove all required Windows Components using [Remove->Remove Windows Components] menu. This failed. Just clicking on the Remove option gave me a message that essentially reads: "Must use version 1809 for this step to take place. Went thru this twice with same result. Can someone please advise me on where I am going wrong here? Thanks
Sorry to answer late, there are problems in my country. Today I made a test with the Windows 10 Pro version and I did not throw sfc errors, previously I had used the Home version, this version is the one of the missing file. Thank you for your great work!
My 1809 installations are all stable. Well, except for one PC where I disabled a service I shouldn't have and it now reboots after waking from sleep... I can't remember which version of the tool kit I used, but I have zero issues with any of the PCs. My installations are always clean installs. I never do in pace upgrades. If there's a need to switch to LTSC 2019 it will be the same process. I guess I should plan to move to LTSC 2019 as, reading between the lines, given how busy you are, a fix for 1903 and beyond may be quite some time away. Awesome job on this toolkit!
Thank you for the detailed explanation. I've done that in the past and it didn't worked. All I got was black screen with a cursor on it. I believe it could be done from the registry but we're gonna need a reg heck, that's exactly why I asked @MSMG for it. The concerned registry entries that needs to be manipulated are: Code: [HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\Themes] "InstallTheme"="%SystemRoot%\\Resources\\Themes\\Default.theme" [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes] "CurrentTheme"="%SystemRoot%\\Resources\\Themes\\Default.theme" HKEY_CURRENT_USER changes needs to be done in the default profile as we are not going to use the copyprofile either. This is an important point.
Should DaRT be integrated as: 1. Integrate to Windows Setup Boot Image. 2. Integrate to Windows Recovery Image The intuitive answer appears to be option 2? . . . When would option 1 be preferred over option 2? Thanks.
1. When booting the ISO, you can go to "repair my pc" and DaRT will be available. 2. On a running system, you can go to the winre environment (reagentc /boottore and next reboot)
0k i use themes only without Wallpapers only Colours . . . if i right by Own wallpapers the 0wn Pictures must copyed over 0gPictures with same Proberties as 0gPictures . . . open 0g aero.theme with Notepad it shows for path Wallpaper=%SystemRoot%\web\wallpaper\Windows\img0.jpg . MayBe copy your own picture that is renamed to - img0.jpg and set to same Securitysettings - into mounted DVD folder . By my knwoledge theme settings are not set in registry but in - .theme files - also for Win to know wich mouse corsur to use is set in - .theme - path to wallpaper is set in - .theme - windowborder colour is in - .theme - and maybe other things. Overall iam an normal consumer user @ all and dont know nothing more as where is a Path but what to set is my mess