"Integrated (Install Pending)" Updates?

  • Thread starter Thread starter Deleted member 763
  • Start date Start date
D

Deleted member 763

Guest
What does this actually mean? Will the updates be installed during setup and will these updates be skipped if I remove the Windows Update Component? And will putting Clean Update Backup to "Complete" make the updates not install?
 
Yes to both questions. Some updates cannot directly update a mounted image and have to run during setup, just like in xp days. Remove windows update and they will fail. Even untouched iso's have updates pending sometimes. Not sure about clean update backup, i would set it to none or compatible.
 
Clanger said:
Yes to both questions. Some updates cannot directly update a mounted image and have to run during setup, just like in xp days. Remove windows update and they will fail. Even untouched iso's have updates pending sometimes. Not sure about clean update backup, i would set it to none or compatible.
Click to expand...

So there is no reason to even install updates if I'm going to remove the Windows Update Component?

Well, that's terrible.
 
Windows update is needed for msu updates language packs and .nets. You could do a live removal once they have all been installed or remove it if you are working on a captured image. It a windows limitation.
 
Clanger said:
Windows update is needed for msu updates language packs and .nets. You could do a live removal once they have all been installed or remove it if you are working on a captured image. It a windows limitation.
Click to expand...

I could, but I'd rather make an ISO that has all the latest security updates and fixes from the get-go without the Windows Update Component, to prevent Microsoft fuckery as much as possible. I suppose I'll have to commit to having no added updates installed with NTLite and remove the Windows Update Components like normal.
 
Your on w10, the forced update malarky is a big no no. You need tokeep up todate so you either keep WU and disable and turn it on when needed, use a WU manager tool, or, and this is just theory, remove WU, extract cab files from msu updates and add them to an image or use dism online to install them on a running system. DISM is part of the 2 Servicing Stack components so you would need to keep them. I dont know if updating with dism works without WU component. I wonder what Nuhi would suggest.
 
Clanger said:
Your on w10, the forced update malarky is a big no no. You need tokeep up todate so you either keep WU and disable and turn it on when needed, use a WU manager tool, or, and this is just theory, remove WU, extract cab files from msu updates and add them to an image or use dism online to install them on a running system. DISM is part of the 2 Servicing Stack components so you would need to keep them. I dont know if updating with dism works without WU component. I wonder what Nuhi would suggest.
Click to expand...

This question is currently for Windows 8.1 though, I'm going to give it a chance, because it comes without the W10 Bullshit, and the UI clusterfuck start menu is easily fixed with Classic Shell, so figured I'd give it a shot. I'm just against Windows Update on 8.1 because security updates (that comes with WU) adds the telemetry client, so i don't want WU to even have a chance to update.
 
8.1 doesnt have the forced updates and wu sneakiness so keep wu and just disabling should be ok, ive had no problems with WU restarting itself on 8.1. Its easier to to mitigate telemetry on 8.1 because ms dont fiddle around with it every month.
 
Clanger said:
8.1 doesnt have the forced updates and wu sneakiness so keep wu and just disabling should be ok, ive had no problems with WU restarting itself on 8.1. Its easier to to mitigate telemetry on 8.1 because ms dont fiddle around with it every month.
Click to expand...

I suppose I could do a live removal of the WU component after setup then.
 
Clanger said:
Try to rename it, take ownership, if that works then keep it.
Click to expand...

I tried to just work around this whole thing and boot into a VM so the updates install and repackage the install.wim with all the updates installed ready to go. But I ran into some other issues now with the errors you see in attached files. It's pretty interesting because all I did was boot in, and repackage with some exceptions to be left out, I guess some of those exceptions left out files NTLite wants. This was my first time attempting something like this, so there is a chance that I did something wrong and the issue has nothing to do with the exclusion list.

This is the exclude list I used with Wimlib-ImageX:

[ExclusionList]
\hiberfil.sys
\pagefile.sys
\swapfile.sys
\System Volume Information
\$Recycle.Bin\*
\Recycler
\Recycled
\Windows\CSC
\winpepge.sys
\$windows.~ls
\$windows.~bt
\Boot
\Recovery
\Recovery.txt
\bootsect.bak
\Program
\ProgramData\Microsoft\Diagnosis\ETLLogs\*
\ProgramData\Microsoft\Network\Downloader\*
\ProgramData\Microsoft\Windows\SQM
\Users\Administratör
\Users\*\NTUSER.DAT*.TM.blf
\Users\*\NTUSER.DAT*.regtrans-ms
\Users\*\NTUSER.DAT*.log*
\Users\*\AppData\Local\Microsoft\Windows\Explorer\*.etl
\Users\*\AppData\Local\Microsoft\Windows\INetCache\IE\*
\Users\*\AppData\Local\Microsoft\Windows\WebCache\*
\Users\*\AppData\Local\Microsoft\Terminal Server Client\Cache\*
\Windows\AppCompat\Programs\Amcache.hve*.TM.blf
\Windows\AppCompat\Programs\Amcache.hve*.regtrans-ms
\Windows\AppCompat\Programs\Amcache.hve*.log*
\Windows\CSC
\Windows\Debug\*
\Windows\inf\*.etl
\Windows\inf\*.ev*
\Windows\inf\*.log
\Windows\Logs\CBS\*
\Windows\Logs\DISM
\Windows\Logs\DPX
\Windows\Logs\dosvc\*
\Windows\Logs\WindowsUpdate\*
\Windows\Logs\PBR
\Windows\Logs\*.log
\Windows\Microsoft.NET\Framework\v2.0.50727\*.log
\Windows\Microsoft.NET\Framework\v4.0.30319\*.log
\Windows\Microsoft.NET\Framework64\v2.0.50727\*.log
\Windows\Microsoft.NET\Framework64\v4.0.30319\*.log
\Windows\Panther\*.etl
\Windows\Panther\*.log
\Windows\Panther\FastCleanup
\Windows\Panther\img
\Windows\Panther\Licenses
\Windows\Panther\MigLog*.xml
\Windows\Panther\Resources
\Windows\Panther\Rollback
\Windows\Panther\Setup*
\Windows\Panther\UnattendGC
\Windows\Panther\upgradematrix
\Windows\Prefetch\*
\Windows\security\database\*.chk
\Windows\security\database\*.log
\Windows\security\database\*.jrs
\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache-S-1-5-21-*.dat
\Windows\ServiceProfiles\LocalService\NTUSER.DAT*.TM.blf
\Windows\ServiceProfiles\LocalService\NTUSER.DAT*.regtrans-ms
\Windows\ServiceProfiles\LocalService\NTUSER.DAT*.log*
\Windows\ServiceProfiles\NetworkService\NTUSER.DAT*.TM.blf
\Windows\ServiceProfiles\NetworkService\NTUSER.DAT*.regtrans-ms
\Windows\ServiceProfiles\NetworkService\NTUSER.DAT*.log*
\Windows\servicing\Packages\wuindex.xml
\Windows\servicing\Sessions\*_*.xml
\Windows\servicing\Sessions\Sessions.back.xml
\Windows\SoftwareDistribution
\Windows\System32\catroot2\*.txt
\Windows\System32\catroot2\*.chk
\Windows\System32\catroot2\*.log
\Windows\System32\catroot2\*.jrs
\Windows\System32\config\*.TM.blf
\Windows\System32\config\*.regtrans-ms
\Windows\System32\config\*.log*
\Windows\System32\config\RegBack\*
\Windows\System32\config\systemprofile\*.TM.blf
\Windows\System32\config\systemprofile\*.regtrans-ms
\Windows\System32\config\systemprofile\*.log*
\Windows\System32\config\TxR\*.blf
\Windows\System32\config\TxR\*.regtrans-ms
\Windows\System32\CodeIntegrity\bootcat.cache
\Windows\System32\LogFiles\AIT\*
\Windows\System32\LogFiles\SQM\*
\Windows\System32\LogFiles\WMI\RtBackup\*.etl
\Windows\System32\SMI\Store\Machine\SCHEMA.DAT*.TM.blf
\Windows\System32\SMI\Store\Machine\SCHEMA.DAT*.regtrans-ms
\Windows\System32\SMI\Store\Machine\SCHEMA.DAT*.log*
\Windows\System32\Sysprep\Panther
\Windows\System32\Sysprep\Sysprep_succeeded.tag
\Windows\System32\wdi\LogFiles\*
\Windows\System32\wfp\*.etl
\Windows\System32\winevt\Logs\*
\Windows\System32\winevt\TraceFormat\*
\Windows\Temp\*
\Windows\WinSxS\ManifestCache\*
\Windows\WinSxS\Temp\*
\Windows\*.log

[CompressionExclusionList]
*.mp3
*.zip
*.cab
*.wmv
*.wma
*.wim
*.swm
*.dvr-ms
\windows\inf\*.pnf
*.rar
*.7z
 
The only time i have seen an unsupported os message is when i super bareboned w7. GImageX v2.2 is a great gui for imagex. There are somethings that are excluded by default, abbodi has posted a list in my capture w7 image thread. Using either the defaults or abbodis list to capture then drag into ntlite hasnt given me any problems so far.
 
Clanger said:
The only time i have seen an unsupported os message is when i super bareboned w7. GImageX v2.2 is a great gui for imagex. There are somethings that are excluded by default, abbodi has posted a list in my capture w7 image thread. Using either the defaults or abbodis list to capture then drag into ntlite hasnt given me any problems so far.
Click to expand...

I didn't remove anything at all, this is a untouched install with just the "pending" updates fully installed. So if I had to guess, I would guess that the problem is with something on that exclusion list.
 
Use the imagex default excludes to start with, with or without gimagex.
 
The WU service malarky is all w10 i believe so 7 and 8.1 should be okay.
 
Clanger said:
Use the imagex default excludes to start with, with or without gimagex.
Click to expand...

It worked fine with just this exclude list, but the install.wim file is 7GB in size, will make a Clean Update Backup (Complete) in NTLite and see how much it removes.

\Boot
\Recovery
\Recovery.txt
\BOOTSECT.BAK
\ProgramData\Microsoft\Network\Downloader\*
\Users\Administrator
\Windows\debug\*
\Windows\inf\*.etl
\Windows\inf\*.log
\Windows\Logs\CBS\*
\Windows\Logs\DISM
\Windows\Logs\dosvc
\Windows\Logs\DPX
\Windows\Logs\PBR
\Windows\Logs\SetupCleanupTask
\Windows\Logs\SIH
\Windows\Logs\WindowsUpdate
\Windows\Logs\DirectX.log
\Windows\Panther
\Windows\Prefetch
\Windows\security\database\*.chk
\Windows\security\database\*.log
\Windows\security\database\*.jrs
\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache-S-1-5-21-*.dat
\Windows\SoftwareDistribution
\Windows\System32\catroot2\*.chk
\Windows\System32\catroot2\*.log
\Windows\System32\catroot2\*.jrs
\Windows\System32\CodeIntegrity\bootcat.cache
\Windows\System32\Sysprep\Panther
\Windows\System32\Sysprep\Sysprep_succeeded.tag
\Windows\System32\winevt\Logs\*
\Windows\Temp\*
\Windows\WinSxS\ManifestCache\*
\Windows\WinSxS\Temp\PendingDeletes\*
\Windows\comsetup.log
\Windows\DtcInstall.log
\Windows\lsasetup.log
\Windows\PFRO.log
\Windows\setupact.log
\Windows\setuperr.log
\Windows\TSSysprep.log.log
\Windows\vmgcoinstall.log
 
I dont worry about the capture image size because ntlite cleans it up very nicely, i done it several times :)
 
Clanger said:
I dont worry about the capture image size because ntlite cleans it up very nicely, i done it several times :)
Click to expand...

"Final Install Size: 15559 MB" Yeah, there is definitely some stuff in there that's not supposed to be there.
 
Caqpture isnt difficult, it took a couple of goes until i got everything right buts its worth it :)
 
Clanger said:
Caqpture isnt difficult, it took a couple of goes until i got everything right buts its worth it :)
Click to expand...

Instead of opening a new thread, I'll just use this one instead to ask you something.

You remove languages from your ISO's (according to your presets), what does that actually do? It says "complete language support removal" is that literal, and means if I play a game and someone has Chinese letters in their names, what happens if I have removed that language from my Windows?
 
You must log in or register to reply here.
Back
Top