Does anyone know how I can apply the .tpk files in the dart pack to my current Windows installation? I'm trying to get DaRT installed on my current machine as I need to copy Toolsx86.cab and Toolsx64.cab from the DaRT installation directory. I'm assuming that the files can be integrated into the wim but I'm not sure how to accomplish this.
Not sure if the files differ from language to language and i'm not familar with the file that is causing you the error. But these are the files in my language pack for Windows 10, build 10.0.19041: Code: Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-LanguageFeatures-OCR-pt-br-Package-amd64.cab Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-LanguageFeatures-Speech-pt-br-Package-amd64.cab Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-LanguageFeatures-TextToSpeech-pt-br-Package-amd64.cab Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-Client-LanguagePack-Package_pt-br-amd64-pt-br.cab Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-Client-LanguagePack-Package_pt-br-amd64-pt-br.esd Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~pt-BR~10.0.19041.1.cab Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-LanguageFeatures-Basic-pt-br-Package-amd64.cab Packs\LanguagePacks\w10\10.0.19041\x64\pt-BR\Microsoft-Windows-LanguageFeatures-Handwriting-pt-br-Package-amd64.cab
hi can someone please help me ? got issue cant fix on my own. Dism restore health doesn't work error 3, CBS shows these issues how to fix it ? CBS Catalog Missing Microsoft-OneCore-DirectX-Database-FOD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 Repair failed: Missing replacement mum/cat pair CBS Package CurrentState Missing Microsoft-OneCore-DirectX-Database-FOD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 CBS Package Visibility Missing Microsoft-OneCore-DirectX-Database-FOD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 CBS Package Owner Missing Microsoft-OneCore-DirectX-Database-FOD-Package~31bf3856ad364e35~amd64~~10.0.22621.1 thanks in advance
Just don't use DISM CleanUp after build 19041. So... Creating a new ISO is the best thing to do. This is already well debated. You can live with that too. It won't harm you.
Code: Download Microsoft-OneCore-DirectX-Database-FOD-Package uupdump.net/findfiles.php?id=356c1621-04e7-4e66-8928-03a687c3db73&q=Microsoft-OneCore-DirectX-Database-FOD-Package Online Dism /Online /Add-Package /PackagePath:C:\Microsoft-OneCore-DirectX-Database-FOD-Package.cab
thanks but it doesnt work. downloaded cab file fom uudump but when running dism add package it stops at 76%.
goto C:\Windows\Logs\DISM delete dism.log run Dism /Online /Add-Package /PackagePath:C:\Microsoft-OneCore-DirectX-Database-FOD-Package.cab again go back to C:\Windows\Logs\DISM read dism.log look for errors to do with Microsoft-OneCore-DirectX-Database-FOD-Package.cab
Toolkit is not meant to "work" with newer monthly updates than the one specified in the changelog due to internal changes of how things work versus what the toolkit does to them. There's also the so called "ghost errors" which are basically a cosmetic that does not impact real world use case.
This support is only related to the part of the Toolkit that deals with component removal. You can use an ISO 22621.1 which is supported by the Toolkit add the updates through the Toolkit and remove the components you want. This is the method that MSMG recommended for intervals between Toolkit updates when new builds are released.
thats what i did downloaded 22621.1 and everything is working as it should no errors . inTerActionVRI maybe you could take look at what toolkit does that makes dism cleanup image corrupt winsxs. for someone who knows what you know is like an hour to fix it then all the win 11 22h2 from 22621.1 to 1702 would work no issues.
any good guides on 'What to exactly remove' from Windows 10 Pro 22H2 10.0.19045.2965 when using MSMG Toolkit, especially in the newest Version? The Video Guides, despite helpful, are from very old versions. Also any tips on how to Edit/Manage the Lists? Which can, kind of, automatize what You want to remove? thanks in advice
As you surmised, this could be a DISM problem. It may be generated after we customize our ISOs. Of course, the components you removed don't need the files that are causing the error after the DISM CleanUP, however... And, it's a big however. The removal process that MSMG has programmed into ToolkitHelper is designed to remove everything that is not needed from the removed components, while retaining parts that are prerequisites for other components to function. And, that's why it's not recommended to use DISM cleanup. Read more here: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1114#post-1726900 But there is one detail that needs testing. I believe that after 18362 CleanUP can be applied without the "/ResetBase" switch Only the "/StartComponentCleanup" switch. If this works, report here. If you integrate netfx35, the presence of pending.xml will cause problems for dism cleanup. Then, do all the necessary procedures, cleanup and integrate NetFX35. If you want to change Toolkit.cmd for testing, replace as below: line 23509 to 23511 from: Code: if "%CleanupOption%" equ "ComponentCleanupResetBase" ( %DISM% /Image:%~1 /Cleanup-Image /StartComponentCleanup /ResetBase ) to: Code: if "%CleanupOption%" equ "ComponentCleanupResetBase" ( if /I "%SelectedSourceOS%" neq "w7" ( if /I "%SelectedSourceOS%" equ "w81" %DISM% /Image:%~1 /Cleanup-Image /StartComponentCleanup /ResetBase if /I "%SelectedSourceOS%" neq "w81" ( if "%ImageBuild%" leq "17763" %DISM% /Image:%~1 /Cleanup-Image /StartComponentCleanup /ResetBase if "%ImageBuild%" gtr "17763" %DISM% /Image:%~1 /Cleanup-Image /StartComponentCleanup ) ) ) Note: Please take a test, to know if In-Place Update will working ok. You need to keep "ManualSetup" Component.
@inTerActionVRI I tested it several times my last one was to use only option 1 2 3 and 4 to remove windows components option 5 6 7 and 8 plus tweaks didn't touch at all made ISO installed and Still when used dism scan health after dism clean up got error 3. I think the issue is somewhere else. From what I learned is that when you use dism scan health dism compares hashes of apps and files in winsxs with probably the ones on windows server or somewhere and if different dism scan health produces error. There's ISO called Ghost Spectre win11 22h2 1702 lite tested it too but I don't trust that one as much as I trust msmg toolkit everything removed in ghost spectre and dism doesn't produce any errors. Actually just now used dism scan health against 22621.1 and got error 3 And been using this version since yesterday lol. heres bit from cbs CheckSur: hrStatus: 0x80070003 [ERROR_PATH_NOT_FOUND], Count of times corruption detected: 1 Failed to run Detect and repair. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] 31034976_3488000883 failed to perform store corruption detect and repair operation Session: 31034976_3488000883 finalized. Reboot required: no [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND dism repair online offline doesnt work Dism++ has option to restore health tried it dism++ says all fixed but Dism says nothing is fixed grrrrr
Did you test it with the modification I suggested? I just made the suggestion. 45 min ago. This will not perform the ResetBase. Now, it's up to you whether or not you take the test.
When you say "ghost specter" it's weird to understand. Because what we say happens is a Ghost SFC error. When talking about "spectre" comes to mind something related to security vulnerabilities. The problem you had must have been a bug related to update 1702. No. It doesn't fix. It just avoids creating new issues in those builds that have the Ghost SFC error issues. I believe that the Ghost SFC error problem has already been solved then for 22621. Thanks for the feedback. In that case, if other people try it out, confirmation feedback is welcome. Thus, we could confirm that the Ghost SFC error was only from 18362 to 22000. Or confirmations that new updates have fixed this issue on 1904x and others. Share this pause to 2077 tweak with us. You can zip and attach it here.
@inTerActionVRI "Share this pause to 2077 tweak with us. You can zip and attach it here." Ghost spectre are team of people not 100% sure where from suspecting Japan, Theyre basically cleaning windows versions of junkware bloatware with every iso version they release theres toolbox attached to it you can use to install uninstall things like store and lots of tweaks etc. you can delete that toolbox if you want. not sure how they made windows update work but if you install updates through WU no bloatware gets reinstalled. to postpone updates i used that toolbox the only thing i was worried about were viruses that could possibly be shipped together with ghost spectre iso did research but havent found anything confirming anyone found some kind of virus. if you want get ghost spectre iso install it and maybe take look at hows done so maybe some things could be adopted and added to msmg toolkit .