| View previous topic :: View next topic |
| Author |
Message |
CrashControl
Joined: 24 Jun 2011
Posts: 1
|
 Posted: Sat Jun 25, 2011 1:36 pm Post subject: Blocked hotfixes, a workaround |
 |
|
| 5eraph wrote: | Updated to 2009-12_1. Please read the Changelog for full details.
As those of you who have downloaded some of the latest x64 hotfixes from Microsoft may have noticed, Microsoft has begun to use "WindowsServer2003" in place of "WindowsServer2003.WindowsXP" in the file names for certain updates. In addition, Microsoft has begun to use the following code in update_SP2QFE.inf:
| Code: | [Prerequisite]
Condition=AndOp,Prereq.XPAMDInstallBlock.Section
..
[Prereq.XPAMDInstallBlock.Section]
PresentOp=CheckReg,HKLM,"SYSTEM\CurrentControlSet\Control\ProductOptions",ProductType,0x00000000
EqualOp=CheckReg,HKLM,"SYSTEM\CurrentControlSet\Control\ProductOptions",ProductType,0x00000000,==,"ServerNT"
Display_String="%WrongProductMessage%" |
This code cannot be altered to force the installer to work with XP x64 without breaking the signature for the INF. Nor can one change the protected registry value without hacking Windows, which we will not discuss here as it borders on piracy. However, some of these updates seem to be intended for XP x64 despite being blocked by the installer. Here is an incomplete list:Microsoft's use of the above code seems to be arbitrary and incorrect in the cases of the updates listed, and perhaps other cases. Therefore, I have decided to include blocked updates in the update pack. |
Hi 5eraph,
First, thank you (and others who contributed) for the comprehensive list of hotfixes maintained in the first post of this thread. Downloading the hotfixes (i.e., those that can't be downloaded automatically) from Microsoft and thehotfixshare.net one-by-one took forever!.  (I wanted the packages for my own installation/integration solutions)
I know the post I'm replying to specifically is dated but having just dealt with this annoying problem myself I wanted to discuss this. I don't want to clutter this thread so perhaps a new one should be created for related issues.
Concerning the blocking of hotfixes, the workaround I used for local installation was to first extract the hotfix into its own directory and then patch the update.exe binary to ignore the "prerequisite" section in the .inf file. All that involves is replacing the appropriate section name in the binary with a dummy value (of equal byte length) that won't be present. Backup the patched update.exe to some other directory so that next time you can just copy over the extracted update.exe with it.
Someone described in a blog (I'll try to dig up the URL if anyone wants it) patching the update.exe to allow modification of the .inf file, but I didn't want to break the signatures of any signed files.
| Code: | fc /b update.orig.exe update.exe
00016A90: 50 44
00016A91: 72 75
00016A92: 65 6D
00016A93: 52 6D
00016A94: 65 79
00016A95: 71 53
00016A96: 75 65
00016A97: 69 63
00016A98: 73 74
00016A9A: 74 6F
00016A9B: 65 6E
00016AA0: 50 44
00016AA2: 72 75
00016AA4: 65 6D
00016AA6: 52 6D
00016AA8: 65 79
00016AAA: 71 53
00016AAC: 75 65
00016AAE: 69 63
00016AB0: 73 74
00016AB4: 74 6F
00016AB6: 65 6E
|
Odd that even the packaged hotfix says that it applies to XP64 in the version info section. It's sad that end-users should be forced to patch MS "fixes" to fix bugs in *their* software. |
|
| Back to top |
|
 |
5eraph
Moderator
Joined: 05 Jul 2005
Posts: 3694
Location: Riverview, MI USA
|
| Posted: Sat Jun 25, 2011 5:32 pm Post subject: |
|
|
Very interesting workaround. Thank you for sharing, and welcome to the forum. 
And you're right, this topic deserves its own thread. |
|
| Back to top |
|
|
yumeyao
Moderator
Joined: 27 Aug 2006
Posts: 1718
Location: Taiyuan, Shanxi, PR China
|
| Posted: Sat Jun 25, 2011 7:30 pm Post subject: |
|
|
breaking update.exe and update.inf's signatures doesn't harm *anything*. The installation resule is transparent for both the OS and the user.
_________________
My work list(Hosted by dumpydooby) |
|
| Back to top |
|
|
5eraph
Moderator
Joined: 05 Jul 2005
Posts: 3694
Location: Riverview, MI USA
|
| Posted: Sat Jun 25, 2011 7:50 pm Post subject: |
|
|
| I could not force updates to install by modifying only the INF. |
|
| Back to top |
|
|
yumeyao
Moderator
Joined: 27 Aug 2006
Posts: 1718
Location: Taiyuan, Shanxi, PR China
|
| Posted: Sat Jun 25, 2011 7:57 pm Post subject: |
|
|
as described above, just patch update.exe.
A patched file can be extracted from my WIC/XPS installers.
_________________
My work list(Hosted by dumpydooby) |
|
| Back to top |
|
|
OnePiece Alb
Joined: 01 Sep 2007
Posts: 265
Location: Albania
|
|
| Back to top |
|
|
5eraph
Moderator
Joined: 05 Jul 2005
Posts: 3694
Location: Riverview, MI USA
|
| Posted: Mon Feb 13, 2012 10:00 pm Post subject: |
|
|
| Further discussion can be found on MSFN. |
|
| Back to top |
|
|
ricktendo64
Joined: 21 May 2006
Posts: 3012
Location: Honduras
|
| Posted: Thu Feb 16, 2012 2:34 pm Post subject: |
|
|
Can the setup from a .net4 patch be modded to ignore digital signature as well?
http://www.mediafire.com/?omrjgqn58hubbee
_________________
Will also accept any old PC hardware donations |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
