xp pro sp3 - many unsigned files ??

Questions about Update Pack making? Ask here.
Post Reply
mineja
Posts: 11
Joined: Fri Mar 07, 2008 9:41 pm

xp pro sp3 - many unsigned files ??

Post by mineja » Mon Oct 06, 2008 7:23 pm

I applied the latest (101) update pack to a copy of xp pro sp3. A clean install using the updated sp3 produced the following list of unsigned files (from setup.log) ...

c:\program files\common files\microsoft shared\triedit\dhtmled.ocx
c:\program files\common files\microsoft shared\triedit\triedit.dll
c:\program files\common files\system\ado\msado15.dll
c:\program files\common files\system\msadc\msadce.dll
c:\windows\apppatch\apph_sp.sdb
c:\windows\apppatch\apphelp.sdb
c:\windows\apppatch\drvmain.sdb
c:\windows\apppatch\sysmain.sdb
c:\windows\explorer.exe
c:\windows\help\apps.chm
c:\windows\system32\crypt32.dll
c:\windows\system32\cscript.exe
c:\windows\system32\d3d9.dll
c:\windows\system32\dhcpcsvc.dll
c:\windows\system32\dnsapi.dll
c:\windows\system32\drivers\afd.sys
c:\windows\system32\drivers\bthport.sys
c:\windows\system32\drivers\disk.sys
c:\windows\system32\drivers\mrxsmb.sys
c:\windows\system32\drivers\ntfs.sys
c:\windows\system32\drivers\rdpwd.sys
c:\windows\system32\drivers\rmcast.sys
c:\windows\system32\drivers\tcpip.sys
c:\windows\system32\drivers\tcpip6.sys
c:\windows\system32\drivers\usbport.sys
c:\windows\system32\es.dll
c:\windows\system32\hnetcfg.dll
c:\windows\system32\inetcomm.dll
c:\windows\system32\ipnathlp.dll
c:\windows\system32\jscript.dll
c:\windows\system32\localspl.dll
c:\windows\system32\mscms.dll
c:\windows\system32\msctf.dll
c:\windows\system32\msexcl40.dll
c:\windows\system32\mshtml.dll
c:\windows\system32\msjet40.dll
c:\windows\system32\msrd2x40.dll
c:\windows\system32\mswsock.dll
c:\windows\system32\ntkrnlpa.exe
c:\windows\system32\ntkrnlpa.exe
c:\windows\system32\ntoskrnl.exe
c:\windows\system32\ntoskrnl.exe
c:\windows\system32\odbc32.dll
c:\windows\system32\osk.exe
c:\windows\system32\psbase.dll
c:\windows\system32\quartz.dll
c:\windows\system32\scrobj.dll
c:\windows\system32\scrrun.dll
c:\windows\system32\shdocvw.dll
c:\windows\system32\shell32.dll
c:\windows\system32\shimeng.dll
c:\windows\system32\tapisrv.dll
c:\windows\system32\urlmon.dll
c:\windows\system32\vbscript.dll
c:\windows\system32\w32time.dll
c:\windows\system32\wbem\cimwin32.dll
c:\windows\system32\wininet.dll
c:\windows\system32\winsrv.dll
c:\windows\system32\wscript.exe
c:\windows\system32\wshext.dll
c:\windows\system32\wshom.ocx
c:\windows\system32\wzcdlg.dll

A signature verification check on the contents of the update pack showed that the unsigned files came from there.

Should I be concerned? Are these supposed to be unsigned? How come? etc etc.

User avatar
code65536
Posts: 735
Joined: Wed Mar 14, 2007 2:58 pm
Location: .us
Contact:

Post by code65536 » Mon Oct 06, 2008 7:40 pm

Something went wrong with your integration, and not all files that should go into svcpack were copied. You might be running into a known bug in the integrator that may result in incomplete truncated integrations. Re-integrate and try again.
My addons: CmdOpen - HashCheck - Notepad2 - MS Runtimes - DirectX

Into the breach, meatbags!

mineja
Posts: 11
Joined: Fri Mar 07, 2008 9:41 pm

Post by mineja » Mon Oct 06, 2008 7:50 pm

perhaps you miss my point or I am missing yours. Example: extract ntfs.sys (5.1.2600.5585) from ryan's update pack - shows as unsigned in signature verifier. That is before the integration. If it is unsigned before, how can it be anything else after? The original (before integration) was a signed version 5.1.2600.5512.
Last edited by mineja on Mon Oct 06, 2008 7:57 pm, edited 1 time in total.

User avatar
5eraph
Site Admin
Posts: 4618
Joined: Tue Jul 05, 2005 9:38 pm
Location: Riverview, MI USA

Post by 5eraph » Mon Oct 06, 2008 7:56 pm

What signature verifier are you talking about? NTFS.SYS does not have certificate built into it. That is what the CAT file is for.

mineja
Posts: 11
Joined: Fri Mar 07, 2008 9:41 pm

Post by mineja » Mon Oct 06, 2008 8:03 pm

In my ignorance (I am learning) I was using Sigverif.exe on different sets of files. But perhaps we have isolated my area of misunderstanding - the cat files. If they in fact carry the signature(s)? and must be married to their file versions then yes, an integration problem.

mineja
Posts: 11
Joined: Fri Mar 07, 2008 9:41 pm

Post by mineja » Tue Oct 07, 2008 1:33 am

Well, I have re-integrated, run a repair install, had a few amd / nvidia driver hiccups on the restart, and I still have a bunch of files unsigned that are supposed to be signed ... rats! How to force replacement of the files and their cat entries??

User avatar
code65536
Posts: 735
Joined: Wed Mar 14, 2007 2:58 pm
Location: .us
Contact:

Post by code65536 » Tue Oct 07, 2008 8:07 am

mineja wrote:perhaps you miss my point or I am missing yours
You are missing mine.

For most system files, the signature exists in a CAT file (sigverif's log will tell you that much if you bothered to check). If the CAT file is not installed, then it will be unsigned according to sigverif. So extracting a file and examining with sigverif it prior to install is pointless. And if you are getting sigverif errors after making a clean install of Windows with your integration disk, then there's a problem with CAT files not being added properly to your integration. As I said, this is a known bug that can hit sometimes.

Look in the I386/SVCPACK directory of your integrated CD. If it looks a little empty, then that's the problem.
My addons: CmdOpen - HashCheck - Notepad2 - MS Runtimes - DirectX

Into the breach, meatbags!

mineja
Posts: 11
Joined: Fri Mar 07, 2008 9:41 pm

Post by mineja » Fri Oct 17, 2008 4:50 am

Turned out the problem was incurred during integration of sp3. I then got all adventurous and had a play with nLite - used it to do the integration of sp3, did clean install and problem gone. Then used nLite again with rvm101 and the problem has stayed away. I got sidetracked in the beginning with the known problems of sp3 (amd etc) because of restart problems during install but the real problem was the MS sp integration procedure I followed - different to what I had used for sp2. Thanks for your help anyway, folks - all sorted.

Post Reply