MSFN Forum: Files in ASMS folder are not integrated by nLite (WinXP x64) - MSFN Forum

Jump to content


If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Files in ASMS folder are not integrated by nLite (WinXP x64) Rate Topic: -----

#1 User is offline   Explorer09 

  • Member
  • PipPip
  • Group: Members
  • Posts: 132
  • Joined: 12-September 11

Posted 29 May 2012 - 11:09 PM

This bug affects three updates for Windows XP Professional x64 Edition.
  • WindowsServer2003.WindowsXP-KB2296011-x64-ENU.exe (MS10-081)
  • WindowsServer2003.WindowsXP-KB2638806-x64-ENU.exe (MS12-006)
  • WindowsServer2003.WindowsXP-KB2659262-x64-ENU.exe (MS12-034)


All of these updates have ASMS folder within. nLite does not integrate the files inside that folder.
This means the nLite'd installation of Windows will still be vulnerable, even though Windows Update would detect that the update are "installed".
In short, nLite fails to directly integrate these updates completely.

Steps to reproduce:
1. Run nLite.
2. Locate a Windows XP Professional x64 Edition (Service Pack 2) disc.
3. Select to integrate "Hotfixes, Add-ons, and Update Packs"
4. Insert these updates:
WindowsServer2003.WindowsXP-KB2296011-x64-ENU.exe
WindowsServer2003.WindowsXP-KB2638806-x64-ENU.exe
WindowsServer2003.WindowsXP-KB2659262-x64-ENU.exe
5. When asking "Do you want to start the process?" Answer Yes.
6. After slipstreaming, open AMD64\ASMS01.CAB that's on the slipstreamed disc.

Result:
The following files should be present in the cabinet, but they are not actually.

amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.4770_x-ww_D89390E2\comctl32.dll
amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_3807D667\comctl32.dll
amd64_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_FAE9D734\GdiPlus.dll
amd64_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.4929_x-ww_32307663\winhttp.dll
Manifests\amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.4770_x-ww_D89390E2.cat
Manifests\amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.4770_x-ww_D89390E2.manifest
Manifests\amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_3807D667.cat
Manifests\amd64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_3807D667.manifest
Manifests\amd64_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_FAE9D734.cat
Manifests\amd64_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_FAE9D734.manifest
Manifests\amd64_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.4929_x-ww_32307663.cat
Manifests\amd64_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.4929_x-ww_32307663.manifest
Manifests\wow64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_8D2E3180.cat
Manifests\wow64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_8D2E3180.manifest
Manifests\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.4770_x-ww_A689AB02.cat
Manifests\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.4770_x-ww_A689AB02.manifest
Manifests\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_C8DFF154.cat
Manifests\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_C8DFF154.manifest
Manifests\x86_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.4929_x-ww_00269083.cat
Manifests\x86_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.4929_x-ww_00269083.manifest
Policies\amd64_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_x-ww_AE43B2CC\5.1.6002.22791.cat
Policies\amd64_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_x-ww_AE43B2CC\5.1.6002.22791.policy
Policies\amd64_policy.5.1.Microsoft.Windows.WinHTTP_6595b64144ccf1df_x-ww_DD275069\5.1.3790.4929.cat
Policies\amd64_policy.5.1.Microsoft.Windows.WinHTTP_6595b64144ccf1df_x-ww_DD275069\5.1.3790.4929.policy
Policies\amd64_policy.5.82.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_C5361FA2\5.82.3790.4770.cat
Policies\amd64_policy.5.82.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_C5361FA2\5.82.3790.4770.policy
Policies\amd64_policy.6.0.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_BD997995\6.0.3790.4770.cat
Policies\amd64_policy.6.0.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_BD997995\6.0.3790.4770.policy
Policies\wow64_policy.6.0.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_5C2DC83C\6.0.3790.4770.cat
Policies\wow64_policy.6.0.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_5C2DC83C\6.0.3790.4770.policy
Policies\x86_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_x-ww_4e8510ac\5.1.6002.22791.cat
Policies\x86_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_x-ww_4e8510ac\5.1.6002.22791.policy
Policies\x86_policy.5.1.Microsoft.Windows.WinHTTP_6595b64144ccf1df_x-ww_7D68AE49\5.1.3790.4929.cat
Policies\x86_policy.5.1.Microsoft.Windows.WinHTTP_6595b64144ccf1df_x-ww_7D68AE49\5.1.3790.4929.policy
Policies\x86_policy.5.82.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_65777D82\5.82.3790.4770.cat
Policies\x86_policy.5.82.Microsoft.Windows.Common-Controls_6595b64144ccf1df_x-ww_65777D82\5.82.3790.4770.policy
wow64_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_8D2E3180\comctl32.dll
x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_5.82.3790.4770_x-ww_A689AB02\comctl32.dll
x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_C8DFF154\GdiPlus.dll
x86_Microsoft.Windows.WinHTTP_6595b64144ccf1df_5.1.3790.4929_x-ww_00269083\winhttp.dll


Update 2012-05-31: I've written a batch script for this. It will create a patched ASMS01.CAB for you. See the attachment.
You also need these binaries:

Then run "update_asms01_cab.cmd".

Update 2012-11-21: Revision 2 of the script. I fixed a version number typo in one of the entries.ini file.
Before: amd64_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_5.1.3790.22791_x-ww_DFCD8D4F
After: amd64_policy.1.0.Microsoft.Windows.GdiPlus_6595b64144ccf1df_5.1.6002.22791_x-ww_DFCD8D4F


Update 2012-11-22: Revision 3. See the last post.

This post has been edited by Explorer09: 26 November 2012 - 10:18 AM


#2 User is offline   Sp0iLedBrAt 

  • MSFN Addict
  • Group: Supreme Sponsor
  • Posts: 1,710
  • Joined: 19-March 09
  • OS:XP Pro x86
  • Country: Country Flag

Posted 30 May 2012 - 02:14 AM

Did you install it on a virtual machine to see if registry entries are written for these updates?

#3 User is offline   Explorer09 

  • Member
  • PipPip
  • Group: Members
  • Posts: 132
  • Joined: 12-September 11

Posted 30 May 2012 - 05:01 AM

View PostSp0iLedBrAt, on 30 May 2012 - 02:14 AM, said:

Did you install it on a virtual machine to see if registry entries are written for these updates?


Before I test that, I want to make sure which part of the registry you are talking about.

Do you want me to check this
HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Installations\*

or this
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Hotfix\*

or both?

EDIT: I tried today installing on a VirtualBox system.
As I expected, only these registry entries are written.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2296011
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2638806
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Hotfix\KB2659262


Files in WinSxS folder are same as the original disc, and this registry key
HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Installations\*

is also not updated.

This post has been edited by Explorer09: 31 May 2012 - 03:59 AM

#4 User is offline   Sp0iLedBrAt 

  • MSFN Addict
  • Group: Supreme Sponsor
  • Posts: 1,710
  • Joined: 19-March 09
  • OS:XP Pro x86
  • Country: Country Flag

Posted 31 May 2012 - 05:18 AM

What about in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

#5 User is offline   Explorer09 

  • Member
  • PipPip
  • Group: Members
  • Posts: 132
  • Joined: 12-September 11

Posted 31 May 2012 - 07:08 AM

My batch script is ready and attached.

By the way...

View PostSp0iLedBrAt, on 31 May 2012 - 05:18 AM, said:

What about in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

I didn't check that, but I think they are updated.
What's the point you are going to make anyway?

This post has been edited by Explorer09: 31 May 2012 - 07:12 PM

#6 User is offline   Kurt_Aust 

  • Master of trial, error & Google
  • PipPipPip
  • Group: Members
  • Posts: 497
  • Joined: 26-April 07

Posted 03 June 2012 - 06:39 AM

Are you able to check if Windows Server 2003 (32-bit) has the same problem?

It seems likely as it also has an ASMS01.CAB though obviously in this case at \I386\

#7 User is offline   Explorer09 

  • Member
  • PipPip
  • Group: Members
  • Posts: 132
  • Joined: 12-September 11

Posted 03 June 2012 - 07:09 PM

View PostKurt_Aust, on 03 June 2012 - 06:39 AM, said:

Are you able to check if Windows Server 2003 (32-bit) has the same problem?

It seems likely as it also has an ASMS01.CAB though obviously in this case at \I386\


No, I don't have the Windows Server 2003 disc. Sorry.

However, it's easy to tell whether the disc is affected. If the disc contains I386\ASMS01.CAB or AMD64\ASMS01.cab or something similar, but does not contain the ASMS subfolder, then the disc is affected.

#8 User is offline   Explorer09 

  • Member
  • PipPip
  • Group: Members
  • Posts: 132
  • Joined: 12-September 11

Posted 22 November 2012 - 07:54 AM

Third revision.

This time I changed many parts of the code to make it easy to add updates.
And it now supports Japanese version of Windows XP/2003 x64.

I hope I can support more languages, but except for English and Japanese, I don't know what to do. I don't have Server 2003 or any of its MUI packs.

Attached File(s)


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy