bigbadmoshe
New Member
On windows V 10 1909 i did not have this issue.
any help is appreciated.
Contents of folder
any help is appreciated.
Contents of folder
FOD Errors
- Thread starter bigbadmoshe
- Start date
Hi,
was that a live edit, on C:\Windows, or an image?
Either way, please try the new version just released (build 7490+).
If it was on an image, then are your FOD CABs exactly for that image version?
Btw .NET FX3 can be alternatively added via the Updates page - Add - Templates - .NET 3.5
was that a live edit, on C:\Windows, or an image?
Either way, please try the new version just released (build 7490+).
If it was on an image, then are your FOD CABs exactly for that image version?
Btw .NET FX3 can be alternatively added via the Updates page - Add - Templates - .NET 3.5
bigbadmoshe
New Member
Official iso from Microsoft. For both.
SW_DVD9_Win_Pro_10_2004_64BIT_English_Pro_Ent_EDU_N_MLF_-2_X22-29752
SW_DVD9_NTRL_Win_10_2004_64Bit_MultiLang_FOD_1_X22-21311
bigbadmoshe
New Member
Tested again with lastest beta build still have same errors
OK, regarding .NET 3.5, enabling works without any FODs added, as the tool pulls it from Sources\SXS folder on the image.
However, if you do ever need .NET 3.5 in the FOD cache (File - Settings - Update cache , .\10.0.2004.x64.FOD), then make sure you have:
microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab
Not just the language pack:
Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~.cab
Tested also with "Microsoft-Windows-LanguageFeatures-Basic-he-il-Package~31bf3856ad364e35~amd64~~.cab"
to enable Hebrew Typing, also worked fine.
Renaming the CAB produced an error "Missing required files" during FOD enabling, not error codes.
Let's see why you have that error:
- What does %temp%\ntlite_dism.log state at the moment of the error? Attach or send it to me please.
Compressed with host's C:\Windows\Logs\CBS\cbs.log at the same moment would be most helpful, if it also contains similar timestamp updates at the very end.
- Confirmed that FOD update cache folder is in the expected location (mentioned above)?
Maybe some other FODs worked for you, that would point to the image issue.
- Was that image modified prior? For testing maybe try just these FODs for now, or enabling .NET, should work without FOD CABs on a default image (with .\Sources\SxS populated with .NET CABs already).
- Is your host DISM operational, can you add FODs manually by scripting or it produces the same error?
You can also check the above logs for more clues on the actual error to not wait on me, if it's obvious, don't spend time on it as there is still a chance that it might be tool related.
However, if you do ever need .NET 3.5 in the FOD cache (File - Settings - Update cache , .\10.0.2004.x64.FOD), then make sure you have:
microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab
Not just the language pack:
Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~.cab
Tested also with "Microsoft-Windows-LanguageFeatures-Basic-he-il-Package~31bf3856ad364e35~amd64~~.cab"
to enable Hebrew Typing, also worked fine.
Renaming the CAB produced an error "Missing required files" during FOD enabling, not error codes.
Let's see why you have that error:
- What does %temp%\ntlite_dism.log state at the moment of the error? Attach or send it to me please.
Compressed with host's C:\Windows\Logs\CBS\cbs.log at the same moment would be most helpful, if it also contains similar timestamp updates at the very end.
- Confirmed that FOD update cache folder is in the expected location (mentioned above)?
Maybe some other FODs worked for you, that would point to the image issue.
- Was that image modified prior? For testing maybe try just these FODs for now, or enabling .NET, should work without FOD CABs on a default image (with .\Sources\SxS populated with .NET CABs already).
- Is your host DISM operational, can you add FODs manually by scripting or it produces the same error?
You can also check the above logs for more clues on the actual error to not wait on me, if it's obvious, don't spend time on it as there is still a chance that it might be tool related.
bigbadmoshe
New Member
Im going to do more tests.
for now i have this from logs.
for now i have this from logs.
Last edited:
bigbadmoshe
New Member
Logs attached
Looks like its something on my side?
Deployment Image Servicing and Management tool
Version: 10.0.19041.1
Error: 32
An initialization error occurred.
For more information, review the log file.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Looks like its something on my side?
Deployment Image Servicing and Management tool
Version: 10.0.19041.1
Error: 32
An initialization error occurred.
For more information, review the log file.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
Last edited:
bigbadmoshe
New Member
No luck.
Logs Errors
Logs Errors
bigbadmoshe
New Member
So after reinstalling windows and trial and error i was missing one package.
E:\NTLite\10.0.2004.x64.FOD\metadata\DesktopTargetCompDB_Neutral.xml.cab
E:\NTLite\10.0.2004.x64.FOD\metadata\DesktopTargetCompDB_Neutral.xml.cab