Jump to content

Recommended Posts

Posted

I download the newest Win7 32 and 64bit updates from three different sources.

1.Wintool Update tool

2.Windows Updates Downloader

3.KUC

and I am getting the error in the pic from DISM. I have never seen this error before. Any thoughts?

I am using a clean offline wim from an untouched Win7 32 and 64bit source

error3aa.jpg

Uploaded with ImageShack.us

Posted (edited)

WinToolkit adds that to the silent installer section because it can't be integrated.

That makes sense. I was just using a script I wrote to slipstream updates to test. I guess DISM caught it and didn't inject the update. I was having another error that I thought was related to this error but it's with a driverpack turns out.

Edited by laddanator
Posted

Yes, this is a known problem.

I integrate it post-install with Add-to-iso\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd

@ECHO off & setlocal EnableDelayedExpansion
SET "LOGFILE=%systemdrive%\install.log"
for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\sources\install.wim set CDROM=%%i:
ECHO>>"%LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM%

:PROCESSOR
:: Detect OS bit-ness on running system. Assumes 64-bit unless 64-bit components do not exist.
SET "ARCH=64"
IF NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" (
IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=32"
)
ECHO>>"%LOGFILE%" 2>>&1 System architecture is %ARCH% bit.
::Begin hotfix install
:Hotfix-install
ECHO>>"%LOGFILE%" ......................
ECHO>>"%LOGFILE%" 2>>&1 Installing required HotFix updates
IF "%ARCH%"=="64" (
WUSA %CDROM%\updates\Windows6.1-KB2533552-x64.msu /quiet /norestart >>"%LOGFILE%" 2>>&1
) ELSE (
WUSA %CDROM%\updates\Windows6.1-KB2533552-x86.msu /quiet /norestart >>"%LOGFILE%" 2>>&1
)


::all processing finished, delete used files, and EXIT::
:CLEANUP
IF EXIST %windir%\Setup\scripts RD /S /Q %windir%\Setup\scripts >nul
endlocal
DEL /F /Q %0% >nul

Posted

I download the newest Win7 32 and 64bit updates from three different sources.

1.Wintool Update tool

2.Windows Updates Downloader

3.KUC

Way too much sources. I recommand only using 2 or 3 (don't know about 1)

  • 1 month later...
Posted (edited)

This (KB2533552) and 3 other updates, whose names escape me are ones that when I log in are still for being installed by WU. Doesn't matter where or how I put them. I've long since given up and remain smug that all other updates are pre-installed so 4 is nothing to worry about.

I will say that the ones that still need to install, if I go to M$ for the off-line installer, I have to verify that I'm running Genuine Windows. That may have something to do with it.

Edited by ElmerBeFuddled
Posted (edited)

I always integrate KB2533552 via $oem$ and setupcomplete.cmd with this code (below), it works and doesnt show up on WU anymore


WUSA Windows6.1-KB2533552-x86.msu /QUIET /NORESTART

Edited by dareckibmw
Posted (edited)

I always integrate KB2533552 via $oem$ and setupcomplete.cmd with this code (below), it works and doesnt show up on WU anymore

Err, Dareck, where do I find/place this $OEM$ folder??

Edited by ElmerBeFuddled
Posted

@ElmerBeFuddled : you have to create the $OEM$ folder in the root of your install source.

But If you use WinToolkit just adding the KB in the silent installs /SFX tab of WinToolkit will be simpler.

WinToolkit adds that to the silent installer section because it can't be integrated.

not in the last versions, have to do it manually.

Posted

So, When I explore my DVD (ISO) file this is what I see.

Capture.png

Have I got the $OEM$ folder in the right place? The updates are inside an $$ folder that's inside the $OEM$ folder. Have I done that right? TBH I've never played with the $OEM$ folder before, ever, so I'm a tad lost!!

Posted (edited)

create folders: $OEM$\$$\SETUP\SCRIPTS then you put KB2533552 hotfix inside folder (SCRIPT) along with setupcomplete.cmd

save this as setupcomplete.cmd and then drop the whole thing in "sources" folder, then save it as an new .iso (I use UltraISO, best for win7, I think)


@echo off
WUSA Windows6.1-KB2533552-x86.msu /QUIET /NORESTART

Edited by dareckibmw
Posted (edited)

Many Thanks. Methinks that will be tomorrows project unless the phone goes and I get some work!!

And I agree about UltraISO. Luckily I have it!

Edited by ElmerBeFuddled
Posted (edited)

create folders: $OEM$\$$\SETUP\SCRIPTS then you put KB2533552 hotfix inside folder (SCRIPT) along with setupcomplete.cmd

Well, I dropped the assembled $OEM$ folder in sources, ran the .iso, nothing there. Methinks I was cracking up, so had a nice brew and a couple of fags before I came back to check everything.

Opened sources, there's $OEM$, opened that, there's $$, opened...........AAAAaaaHH!!! Therein lies my problem! The folder wasn't named $$ at all, it was named %%!! Dufus that I am!

Edited by ElmerBeFuddled

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...