Non-tool report - Windows 7 End Of Extended Support DISM package removal issues. DISM broken?

  • Thread starter Thread starter Clanger
  • Start date Start date
C

Clanger

Guest
Is anyone else having problems with w7(updated to end of extended support, sysprepped captured and deployed) dism live package removals, manually with command line, not 3rd party tools(although the problem also happens with a 3rd party tool)? Is it me with a bad build or is it an ms problem and if its a dism issue(dism broke) would it affect NTLite?

Full list of updates and additions(IE11 and .Net 4.8)
F:\ZZ-IGNORE\WINDOWS 7\group1\01-2016-07-27-windows6.1-kb3177467-x64-SS.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\02-2016-04-25-windows6.1-kb3125574-v4-x64-SP2.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\03-2016-03-29-windows6.1-kb3145739-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\04-2016-04-10-windows6.1-kb3153199-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\05-NET-Framework-4.8-x86-x64-allos-enu.exe
F:\ZZ-IGNORE\WINDOWS 7\group1\07-2012-09-windows6.1-kb2729094-v2-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\08-2013-02-windows6.1-kb2670838-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\09-2013-07-windows6.1-kb2834140-v2-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\10-IE11-Windows6.1-x64-en-us.exe
F:\ZZ-IGNORE\WINDOWS 7\group1\11-2011-11-windows6.1-kb2639308-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group1\12-2016-09-ie11-windows6.1-kb3185319-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2012-04-windows6.1-kb2667402-v2-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2012-04-windows6.1-kb2676562-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2012-06-windows6.1-kb2698365-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2013-02-windows6.1-kb2813347-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2013-11-windows6.1-kb2862330-v2-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2013-11-windows6.1-kb2894844-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2013-12-windows6.1-kb2912390-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2014-09-windows6.1-kb2984972-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2015-01-windows6.1-kb3004375-v3-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2015-03-windows6.1-kb3046269-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2015-04-windows6.1-kb3059317-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group2\2015-12-windows6.1-kb3110329-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2015-12-windows6.1-kb3123479-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2016-04-windows6.1-kb3150220-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2016-04-windows6.1-kb3155178-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2016-04-windows6.1-kb3156016-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2016-05-windows6.1-kb3159398-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2016-05-windows6.1-kb3161949-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2017-08-windows6.1-kb4040980-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2019-02-windows6.1-kb4490628-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2019-08-windows6.1-kb4474419-v3-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2020-01-windows6.1-kb4536952-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group3\2020-01-windows6.1-kb4539601-x64.msu
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\01-SS windows6.1-kb5017397-x64_2a9999bd20cb964869c59bb16841a76e14030a29.msu
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\02-CU windows6.1-kb5022338-x64_75d100c03bcaee4b62d08004cc382337ed09d327.msu
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\03-IE11-CU windows6.1-kb5019958-x64_7bf51f3d84c14dbed19e1acd35b921594ab603b9.msu
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\04-windows6.1-kb5020861-x64_9df527e79d8854a4ed1b8fe26c2a66bca7d6b8da.msu

Dont remember having this issue on a previous captured EoL(only) wim, just this EoEs.

Observation, all packages im exporting and removing are showing "packagename - 6.1.7601.17514, nothing is showing higher than 17514 and its happened on 2 deployments.
 
Last edited by a moderator:
Have you tried same updates integrated with NTLite and nothing else done, if you reload the image, are packages updated, were there errors during integration?
Or the sysprepped image was Windows-Updated to the latest?
Same applies, you can use NTlite to install updates as well, not just integrate. Source - Tools - Install updates
 
Nothing was integrated with the tool, fresh iso, manually updated at oobe, captured, cleaned out with the tool(no removals, just cleaned), deployed by extracting wim file to a partition that already has a boot loader entry, then i tried the removals. Thats why i put Non tool report in the title.
See im thinking that if its dism is broken and its the host too it might affect ntlite. I dont think its a bad install, 99.9% not user error and it didnt happen on a previous EoL capture either, just these new EoES updates. Slim chance it might have been ntlite during the cleaup run but i dont think so.
Can easily redo, get any error codes that show in the command window and dism log.
 
Last edited by a moderator:
I am planning on doing this for my wife's old laptop that I upgraded from vista to 7. Once I try it out will let you know if I encounter any issues.
 
Necrosaro deploy the image, NO removals, then do manual dism live removals, start with anytime upgrade then the localpacks, us gb za etc. Im not seeing this anywhere else and the latest CU doesnt state its for Pro edition either.

End Of Life capture was fine, something in these 4 is causing it
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\01-SS windows6.1-kb5017397-x64_2a9999bd20cb964869c59bb16841a76e14030a29.msu -- ?
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\02-CU windows6.1-kb5022338-x64_75d100c03bcaee4b62d08004cc382337ed09d327.msu -- ?

doubt it but here goes anyway
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\03-IE11-CU windows6.1-kb5019958-x64_7bf51f3d84c14dbed19e1acd35b921594ab603b9.msu
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\04-windows6.1-kb5020861-x64_9df527e79d8854a4ed1b8fe26c2a66bca7d6b8da.msu

I'll redo it but with the capture as is, not ntlite cleaned version, then the cleaned version.
I wonder if abbodi86 has heard anything.
I want to reload one of my laptops back to near factory spec with an updated w7 pro too.
 
Last edited by a moderator:
Another thing i could do is install untouched iso, package removal at oobe, then update and capture and pray those packages didnt reappear.
 
Clanger said:
Necrosaro deploy the image, NO removals, then do manual dism live removals, start with anytime upgrade then the localpacks, us gb za etc. Im not seeing this anywhere else and the latest CU doesnt state its for Pro edition either.

End Of Life capture was fine, something in these 4 is causing it
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\01-SS windows6.1-kb5017397-x64_2a9999bd20cb964869c59bb16841a76e14030a29.msu -- ?
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\02-CU windows6.1-kb5022338-x64_75d100c03bcaee4b62d08004cc382337ed09d327.msu -- ?

doubt it but here goes anyway
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\03-IE11-CU windows6.1-kb5019958-x64_7bf51f3d84c14dbed19e1acd35b921594ab603b9.msu
F:\ZZ-IGNORE\WINDOWS 7\group4-esu\04-windows6.1-kb5020861-x64_9df527e79d8854a4ed1b8fe26c2a66bca7d6b8da.msu

I'll redo it but with the capture as is, not ntlite cleaned version, then the cleaned version.
I wonder if abbodi86 has heard anything.
I want to reload one of my laptops back to near factory spec with an updated w7 pro too.
Click to expand...
Will let you know maybe sometime tomorrow how it goes.
 
Clanger said:
Im gonna start mine once ive had breakfast and tea.
Click to expand...
I won't be able to do mine till night time since I have a toddler bum to take care of during the day and stock market work early as well.

Earl Grey tea....hot?
 
Test - using captured wim as is, not like previous tests with ntlite cleaned wim, problem still happens, so thats ruled ntlite out.
1 - running anytime upgrade.bat as administrator, all failed
2 - ran again, this time elevated with power run, partial success only

all log files from installation onwards.
 

Attachments

I cannot seems to understand what's the issue exactly
you are trying to remove inbox OS packages? that don't work normally
and the registry changes you are trying to made are blocked, because CBS registry require TrustedInstaller privileges

and OS packages are all 6.1.7601.17514, the version don't change with updates
 
Clanger said:
Test - using captured wim as is, not like previous tests with ntlite cleaned wim, problem still happens, so thats ruled ntlite out.
1 - running anytime upgrade.bat as administrator, all failed
2 - ran again, this time elevated with power run, partial success only

all log files from installation onwards.
Click to expand...
I still haven't had a chance to try anything yet. My kid thinks that sharing a cold is caring.
 
I usually do it elevated anyway but i did not see that error on the EoL build ive been using for nigh on 2 years so i floated it here see if anyone else has had problems, if you reckon its alright and as no one else has a problem i can carry on then, thanks abbodi86
 
: Error Code 0x80070005 — also known as 'Access Denied' error — is a type of Windows update error. It occurs when the system or user lacks the required files or permissions to change settings at the time of Windows update.
Click to expand...
 
You must log in or register to reply here.
Back
Top