Windows 7 Hotfix repository

You cant.Only way is reverse wim capture.

 

Or via runoonce.

 

How dism.exe prioritize adding hotfixes to the image? Is it by name or what?

 

After installing the latest updates released by SoLoR, on the restart, I am getting a black screen with a pop up window saying "interactive logon has failed. Please consult the event log for more details." This is the only thing that pops up. Once I click OK, it's just a black screen. Any way to fix this?

 

Any idea how to fix this? I just ran into this exact problem.

 

Any idea how to fix this? I just ran into this exact problem.

 

Give some time for people to answer, asking the same thing every 8 minutes is no good if nobody is currently online to answer it!

The important thing is too have all the updates installed, have you got all of them installed, including KB2619234, and how were they installed?

 

You need to login to view this posts content.

 

Sorry about that. Tried to edit my posts earlier, but couldn't do so on the mobile version. Anyways, when it comes to updates like this, I use the automatic installer. I think it was created by George King from a previous update thread, so I'm not exactly sure which updates were installed, & which ones weren't.

 

Hello,

I did a clean install of Windows 7 with all updates of Solor (integrated in ISO)
and since when I close internet explorer (IE8 64-bit) 1 out of 2, the process iexplorer.exe does not disappear in task manager (forced to kill)

what could be the problem?
and I don't want IE9

for IE8, I just integrated the last update of IE8 available on the link of komm
the problem could come from an update of IE8?

thanks

 

You need to login to view this posts content.

 

The Mystery of the Installation of Updates

I was always angry about the matter that, if I found a new update of a component or feature, that I had not activated, it does not apply to the system.

Installation stops with the error message:
View attachment 12073


If I activate the feature or component later, I always have to look for all the updates and hotfixes that are available for that feature or component. For example I did not have IIS activated IIS on my system, so all updates/hotfixes that are for IIS only, will not apply to the system. If I decide or need IIS later, I have to install the updates again. This is double work or IT by food.

Yesterday I found out, that this only happens, if I try to apply the update by just clicking on the .MSU file.

What did I have done?
I inspected my system with

Code:

dism /online /Get-packages /Format:table >Packages.txt
dism /online /Get-features /Format:table >Features.txt

to see what windows updates were installed.

I saw that some of the updates where only installed in the _BF version but not in the GDR version.
Normally I install both of them.

If an update is marked as a “force LDR” update in my list, I used

Code:

dism /online /add-package /packagepath:"%ldrdir%\update-bf.mum" /NoRestart

to force LDR installation and

Code:

start /wait wusa.exe "%updatename%.msu" /quiet /norestart

to install the GDR.

So the different ways of installation must have been the reason for the behaviour that the LDR version was installed but the GDR wasn’t.


Then I tried the installation of the update via

Code:

dism /online /add-package /packagepath:"%ldrdir%\update.mum" /NoRestart

and voila: the GDR version installs with no problems. Clicking on the .msu shows:
View attachment 12074
(KB2489256 is a (superseded) IIS update that normally only applies if IIS is enabled)


So the best way of installing updates is indeed the following code:

Code:

dism /online /add-package /packagepath:"%ldrdir%\update-bf.mum" /NoRestart
and then
dism /online /add-package /packagepath:"%ldrdir%\update.mum" /NoRestart

(This is also the way SoLoR’s “update.cmd” or burfadel’s “Installer for Windows Updates” work)

Note, that an update for a feature or addition that is not installed will not apply this way.
You must install the feature first!
You can disable it but it has to be present on your system. Also, if you have installed a higher version of a feature (like IE9) you can’t apply updates for the previous version of this feature (like IE8).

Also note that there is no need to install both, the LDR and the GDR version. The LDR is enough.
Only if you want to avoid the Windows “An update is available” message the GDR version may be needed.

I post this, although I know, that most of you know this. But there will be the one or the other novice like me, for whom this might be of interest.

 

You need to login to view this posts content.

 

Thanks for adding the outlook-x-none.msp update. There are also newer updates available for ipeditor-x-none.msp & infopath-x-none.msp in infopath2010-kb2596555-fullfile-x??-glb.exe. (14.0.6109.5004 vs. 14.0.6105.5000 currently in repository). They can be found on the MS page for KB2584066.

 

I'm looking for the latest version of IE 9 in French, someone would have a link?

we can integrate it as an update?

thanks

 

MS NET4 Framework Client x64-x86 Silent Installer - Oktober, 2011 ?

 

I need some help with batch coding. The script is based on solor's update.cmd. Problem with my script is, kb982861 appears 3 times. I'm not quite sure what I'm doing wrong. Any help? I'm not very good in batch scripting haha.
The whole idea is to integrate certain hotfixes in order first before integrating everything else. I am aware of burfadel's script which integrates in certain order too but it's a bit too complicated for me haha.

test.cmd:

Code:

:: temporary folder for extracted cab files. the files are already there so i didn't include the code to expand files.
set solortemp=Z:\solor\temp
:: solor's root folder, and a single ie9 folder with hotfixes resides inside too.
set updatespath=W:\win7\updates.solor

for /f  "tokens=*" %%f in (priolist.txt) do (
for /f "tokens=*" %%a in ('dir /b /a:d "%solortemp%\updates.install\unpacked\*%%f*"') do (
dir "%solortemp%\updates.install\unpacked\*%%f*"
)
for /f "tokens=*" %%b in ('dir /b /a:d "%updatespath%"') do (
for /f "tokens=*" %%a in ('dir /b "%solortemp%\updates.install\%%b\*.cab"') do (
for /f "tokens=*" %%a in ('dir /b /a:d "%solortemp%\updates.install\%%b\unpacked\*%%f*"') do (
dir "%solortemp%\updates.install\%%b\unpacked\*%%f*"
)
)
)
)

priolist.txt:

Code:

kb982861
kb2619234

 

That project looks interesting but there are more current updates available here than in that pack. Here's a quick comparison:

His includes KB2567053 which updates Win32k.sys to 6.1.7601.21811. Here, the pack includes KB2618837-v3 which updates Win32k.sys to 6.1.7601.21827.

His includes KB2567680 which updates Kernel32.dll to 6.1.7601.21772. Here, we've got KB2615701 which updates to 6.1.7601.21824

His: KB2563894 updates Tcpip.sys to 6.1.7601.21754. Here: KB2459530-v3 updates to 6.1.7601.21789

His: KB2556532 updates Ntoskrnl.exe to 6.1.7601.21755. Here: KB2566205-v2 updates to 6.1.7601.21789

His: KB2544893 updates Inetcomm.dll to 6.1.7601.21719. Here: KB2554876-v2 updates to 6.1.7601.21734

His: KB2536276 updates Mrxsmb10.sys (and others) to 6.1.7601.21767. Here: KB2612966 updates to 6.1.7601.21819

His: KB2503665 updates Afd.sys to 6.1.7601.21712. Here: KB2579274 updates to 6.1.7601.21792

His: KB2476490 updates Oleaut32.dll to 6.1.7601.21669. Here: KB2564958 updates to 6.1.7601.21802

His: KB2511250 updates Xpsgdiconverter.dll to 6.1.7601.21667. Here: KB2620393 updates to 6.1.7601.21822

His: KB2509553 updates Dnsrslvr.dll to 6.1.7601.21673. Here: KB2520155 updates to 6.1.7601.21689

His: KB2507618 Here: KB2555392

His: KB2506212 Here: KB2584577

And there are other superseded ones in his. There are just many more eyes looking out for the latest updates on this site.

 

You need to login to view this posts content.