[wondras]

nuhi, on Jul 14 2007, 10:43 AM, said:

JJA, nlite should have done that for you, it keeps a clean backup of the file. I wonder why it didn't happen. If you find out how to duplicate that issue, installed with some other method other than booting from the cd or running winnt32 or you tampered with the installation let me know, thx.

Greetings!

I just registered for this forum so I could post a bit more info, in hopes of leading a few more people to this thread via Google searches and such...

I ran into this same problem -- new flash drives prompted for administrator credentials to install. (Actually, they seemed to function anyway, but still gave the scary admin dialog.) I followed many false trails trying to resolve this: permissions on the USBSTOR.INF file, PartMgr.sys upper filter registry entries, etc. There were lots of theories on the InterWeb about what could cause this, but not many answers.

Eventually I traced it as JJA did, to an error in setupapi.log about an unsigned version of SysSetup.dll. I guess nLite created a modified version of this file, as well as sfcfiles.dll, to change some behavior during the initial installation of Windows. I didn't see any backups of the original versions of these files, but admittedly I wouldn't have known where to look. Copying clean dlls from a vanilla XP machine fixed it right up.

I used nLite v1.3.5 with an XP Pro SP2-slipstreamed-on-SP1 disc as the source. I didn't change anything outside of the nLite GUI options.

Despite this problem, I must say that nLite is one fantastic utility. I was able to install XP on a slew of PCs with Intel DP35DP motherboards that need SATA drivers and have no floppy controller to load it with F6 during setup. Ironically, the boards come with a floppy containing the drivers!

Thanks for your hard work, and keeping up with the moving target that is Microsoft!

-Warren.

[Madhits45]

JJA, on Jul 13 2007, 02:48 PM, said:

Hi, I am not sure if the topic is still actual, but I found the solution to the "administrators credentials" problem when connecting USB devices. Looking in C:\Windows\setupapi.log there was rows about incorrect C:\Windows\system32\syssetup.dll. This file must have been modified when I was creating n-lite image. I simply replaced this file from flat installation of WinXP and I don't get the credentials window when connecting USB key, USB mouse etc. when the non-administrative user is logged on.

This is interesting. I do not have the remove catalog files option checked for my windows 2003 disc and i still get the pop up for installing drivers for common usb devices (thumb drives). This syssetup.dll could be why. I recall a district difference between the issue with windows xp and prob the same in 2003. XP & 2003, if you removed the catalog files you had to install the device before you could see it in my computer. With 2003 & prob xp this syssetup.dll issue I can actually use the device and ignore the install. Once I install it though then the device is named properly in my computer. Also could this be tied to explorer not auto mounting some USB hard drives. I have to go into disk management and give the USB hard drive a drive letter for it to show up. I am going to try replacing syssetup.dll with the original from the disc and see what happens. THANKS for the info. Nuhi it seems we have found another bug.

Sure enough.. I have the errors in setupapi.log Look like this..

#W360 An unsigned, incorrectly signed, or Authenticode™ signed file "C:\WINDOWS\system32\SysSetup.Dll" for driver "System devices" will be installed (Policy=Ignore). Error 87: The parameter is incorrect.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.

Attached File(s)

•  Last_Session.ini (24.24K)
  Number of downloads: 1

This post has been edited by Madhits45: 23 September 2007 - 09:47 AM

[Madhits45]

I tried changing out my syssetup.dll on my installed system and it still asks for the drivers to be installed. Does this work or do I need to reinstall the system in order for that fix to take? If I have to reinstall why is that? Is there a reg entry I can change back to default to get it to stop prompting for drivers for common USB devices?

THANKS

[Madhits45]

OK total suckage. I changed out the syssetup.dll with the one from the original CD and now I get an error during setup. The error says:

The signature for windows setup is invalid. The error code is 57.
The parameter is incorrect.

Fatal error :
Setup failed to install the product catalogs. This is fatal


Shoot I have to use the nlite patched version of syssetup.dll as it is the only one that works with the install. Nuhi this is a issue I cant fix on my own. Can you fix this in the next version of nlite.

Or if perhaps I missed something here. Can someone explain what else I can do to get around this issue manually?

THANK YOU

This post has been edited by Madhits45: 25 September 2007 - 01:32 PM

[fromthewoods]

JJA, on Jul 13 2007, 01:48 PM, said:

Hi, I am not sure if the topic is still actual, but I found the solution to the "administrators credentials" problem when connecting USB devices. Looking in C:\Windows\setupapi.log there was rows about incorrect C:\Windows\system32\syssetup.dll. This file must have been modified when I was creating n-lite image. I simply replaced this file from flat installation of WinXP and I don't get the credentials window when connecting USB key, USB mouse etc. when the non-administrative user is logged on.

nuhi, on Jul 14 2007, 07:43 AM, said:

JJA, nlite should have done that for you, it keeps a clean backup of the file. I wonder why it didn't happen. If you find out how to duplicate that issue, installed with some other method other than booting from the cd or running winnt32 or you tampered with the installation let me know, thx.

Hi JJA and nuhi,

First off let me say nLite is a great tool and I've been using it for a few months now.

I ran into this USB driver issue as well recently and thanks to JJA's work, replacing the syssetup.dll from a non-nlite'd system gets rid of this issue. As JJA mentioned above, I looked in the setupapi.log and noticed the same error regarding this .dll.

nuhi:
I am using a Windows XP SP 2 Volume Licensed edition hologrammed CD to create my nlite session. Once I rip all the files to my drive I use the nLite normally and create a bootable ISO. I burn it with Nero 7 and boot off the CD and install Windows normally. I have recreated my nlite'd session many times using my original CD from Microsoft and I still get this issue. Even just adding a couple of drivers to support ICH8 SATA controllers still affects this .dll. I am not sure what happens but it probably needs some attention.

Please let me know if you need any more information.

Thanks
fromthewoods

[fromthewoods]

Madhits45, on Sep 25 2007, 12:19 PM, said:

OK total suckage. I changed out the syssetup.dll with the one from the original CD and now I get an error during setup. The error says:

The signature for windows setup is invalid. The error code is 57.
The parameter is incorrect.

Fatal error :
Setup failed to install the product catalogs. This is fatal


Shoot I have to use the nlite patched version of syssetup.dll as it is the only one that works with the install. Nuhi this is a issue I cant fix on my own. Can you fix this in the next version of nlite.

Or if perhaps I missed something here. Can someone explain what else I can do to get around this issue manually?

THANK YOU

I'm assuming when you say you are copying the syssetup.dll file from the CD you mean the file syssetup.dl_ in the I386 folder. This file on the CD (at least mine) is 321KB. The syssetup.dll file under C:\Windows\System32 is 961KB. I don't think you can just copy the file and rename it and put it in the proper folder. The file size is different. Try copying it from a working system.

Thanks,
Fromthewoods

[Madhits45]

fromthewoods, on Sep 25 2007, 05:26 PM, said:

I'm assuming when you say you are copying the syssetup.dll file from the CD you mean the file syssetup.dl_ in the I386 folder. This file on the CD (at least mine) is 321KB. The syssetup.dll file under C:\Windows\System32 is 961KB. I don't think you can just copy the file and rename it and put it in the proper folder. The file size is different. Try copying it from a working system.

Thanks,
Fromthewoods

Yes I copied the syssetup.dll from the original windows 2003 sp2 disc. Its cabed and renamed syssetup.dl_. I extracted it with winrar and put it in my current system32 folder but that did not work. Still forces me to run through install of common mass storage USB devices and also forces you to manually mount USB hard drives.

So then I tried replaced the syssetup.dl_ on my nlited disc with the original from the 2003 sp2 disc and reburned my disc but this also did not work. I get an error during setup like I indicated earlier. This is because nlite edits the syssetup.dll so it can skip OOBE I believe. In any case there is an issue with the way nlite does this edit and this is the bug that nuhi will have to look at.

[fromthewoods]

wondras, on Sep 13 2007, 07:37 AM, said:

nuhi, on Jul 14 2007, 10:43 AM, said:

JJA, nlite should have done that for you, it keeps a clean backup of the file. I wonder why it didn't happen. If you find out how to duplicate that issue, installed with some other method other than booting from the cd or running winnt32 or you tampered with the installation let me know, thx.

Greetings!

I just registered for this forum so I could post a bit more info, in hopes of leading a few more people to this thread via Google searches and such...

I ran into this same problem -- new flash drives prompted for administrator credentials to install. (Actually, they seemed to function anyway, but still gave the scary admin dialog.) I followed many false trails trying to resolve this: permissions on the USBSTOR.INF file, PartMgr.sys upper filter registry entries, etc. There were lots of theories on the InterWeb about what could cause this, but not many answers.

Eventually I traced it as JJA did, to an error in setupapi.log about an unsigned version of SysSetup.dll. I guess nLite created a modified version of this file, as well as sfcfiles.dll, to change some behavior during the initial installation of Windows. I didn't see any backups of the original versions of these files, but admittedly I wouldn't have known where to look. Copying clean dlls from a vanilla XP machine fixed it right up.

I used nLite v1.3.5 with an XP Pro SP2-slipstreamed-on-SP1 disc as the source. I didn't change anything outside of the nLite GUI options.

Despite this problem, I must say that nLite is one fantastic utility. I was able to install XP on a slew of PCs with Intel DP35DP motherboards that need SATA drivers and have no floppy controller to load it with F6 during setup. Ironically, the boards come with a floppy containing the drivers!

Thanks for your hard work, and keeping up with the moving target that is Microsoft!

-Warren.

Wondras,

Just a quick question: How were you able to find that nLite modified the sfcfiles.dll as well?

Thanks,
Fromthewoods

[Madhits45]

Its the options to turn off WFP windows file protection. Nlite has had that option for years. That file has to be altered so that you can have an nlited install. After the install is done you can either Turn it back on or leave it off.

I always leave WFP off and thus keep the modified sfc dll in place.

If someone else could please confirm this issue is in 2003 also I would like to know if there is a way around it like there appears to be in XP. Why the xp trick does not work for me I don't know. If it should what am I missing?

THANKS

[nuhi]

wondras, thanks. nLite should have done that on it's own, you can find the command in the nlite.inf.
But this helps a lot because I didn't know that the function failed for some reason, at least it will be easier to debug now.

Things which trigger syssetup patching are:
- patches
- component removal
- ie7 integration
- addons which edit syssetup.inf

Btw nLite backups clean syssetup.dll to the syssbck.dll in the i386 folder, just extract that, it should be the clean version. If it's not then that is the problem, maybe you ran nlite more than once and it didn't detect the clean version properly on the second run.

edit: tried it now with all removed and the backup was restored just fine. If someone finds out how to break this yell.
Also check windows\setuperr.log for errors, maybe your nlite.inf never got executed if something else broke before it.

[Madhits45]

nuhi, on Sep 28 2007, 03:24 AM, said:

wondras, thanks. nLite should have done that on it's own, you can find the command in the nlite.inf.
But this helps a lot because I didn't know that the function failed for some reason, at least it will be easier to debug now.

Things which trigger syssetup patching are:
- patches
- component removal
- ie7 integration
- addons which edit syssetup.inf

Btw nLite backups clean syssetup.dll to the syssbck.dll in the i386 folder, just extract that, it should be the clean version. If it's not then that is the problem, maybe you ran nlite more than once and it didn't detect the clean version properly on the second run.

edit: tried it now with all removed and the backup was restored just fine. If someone finds out how to break this yell.
Also check windows\setuperr.log for errors, maybe your nlite.inf never got executed if something else broke before it.

NUHI... THANK YOU, THANK YOU :-). This is the kinda info I have begged you for in the past with regards to how nlite does things. I know you don't wanna give away all the secrets but MAN is this kinda info is VERY useful.

I have determined that in my windows 2003 disc that the syssbck.dl_ is the original. The nlite.inf is not replacing the original file back in my case. Nlite.inf is executed from cmdlines.txt. Its done with this line in cmdlines.

"rundll32 advpack.dll,LaunchINFSection nLite.inf,nLiteReg"

I did change the order of this file and made yours last. This I dont believe can cause an issue. I found the line that replaces the sysetup.dll was missing from my nlite.inf. That was my problem. THANKS

I will look through the nlite.inf and see what else might be missing.

THANK YOU AGAIN.. problem solved.. now time to test it out.

This post has been edited by Madhits45: 28 September 2007 - 12:17 PM

[nuhi]

Madhits45,
how is it possible that that the line (movex syssbck ...) is missing from your nlite.inf?
Maybe you think that I should know that but it simply seems not possible, even though I hope that's the case and we find out why.

Do you (all with this issue of not having the restored file) run Windows by setup.exe (winnt32.exe) or use your own winnt.sif file or anything that would skip this portion?

Because by just using nLite with it's Unattended options should be fine.

[Madhits45]

nuhi, on Sep 28 2007, 12:55 PM, said:

Madhits45,
how is it possible that that the line (movex syssbck ...) is missing from your nlite.inf?
Maybe you think that I should know that but it simply seems not possible, even though I hope that's the case and we find out why.

Do you (all with this issue of not having the restored file) run Windows by setup.exe (winnt32.exe) or use your own winnt.sif file or anything that would skip this portion?

Because by just using nLite with it's Unattended options should be fine.

NUHI.. There must be something else. I thought this line was missing from my nlite.inf.

HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_s05",0x00020000,"nhelper moveex ""%17%\syssbck.dll"" ""%11%\syssetup.dll"""

However it is there and I believe working. Yet I still get the errors in setupapi.log saying that my syssetup.dll is not signed. What else could be causing this? Does the dll need to be re-registered in order to work?

I do use my own winnt.sif file but it was one that was originally created by nlite. What line could be missing from that? nlite.inf is run from cmdlines.txt I thought. The entry for it is there.

I am stilling getting the pop up for common USB devices. Whats strange is they do mount and can be used but the pop up to install them comes up.

If you can share any more of your insight on how the nlite.inf does what it does, then I should be able to fix this issue on my own.

PLEASE LET ME KNOW>
THANKS

This post has been edited by Madhits45: 03 October 2007 - 03:51 PM

[nuhi]

There is no secret, why are you constantly aiming towards that is beyond me.

Are you sure that the syssetup.dll is exactly the syssbck.dll now, did you overwrite it by hand?

Did you remove CAT files?

[Madhits45]

nuhi, on Oct 4 2007, 04:21 AM, said:

There is no secret, why are you constantly aiming towards that is beyond me.

Are you sure that the syssetup.dll is exactly the syssbck.dll now, did you overwrite it by hand?

Did you remove CAT files?

Nuhi,

1. In general what I'm getting at is I would like to understand some of the stuff that nlite does behind the scenes, the not so obvious things. Like a list of dlls it edits etc, or how they are edited. I think if more of this was understood by some of the members here we could better fix our own problems. OR find what were doing that is messing up nlite.

2. I checked both my syssetup.dll and syssbck.dll they are both correct & in my i386 before install, yet the replacement never happens by the nlite.inf during install. I am not sure why. I have even replaced the original sysssetup.dll back after the install and that does not fix the problem. I'm not sure why that is unless this dll has another dll that must also be replaced or needs to be re-registered or a reg entry also must be changed.

3. I do not remove the cat files. Like I said when you remove the cat files its like windows has no idea what the usb device is. This is different it knows what the device is but still forces you to install the device. Could the cat files be removed without checking that in nlite? and could this cause the setupapi.log errors I'm still getting about syssetup.dll (An unsigned, incorrectly signed syssetup.dll)

In any case is there any more that could be causing the problem? Or have i got it all?

THANKS

This post has been edited by Madhits45: 04 October 2007 - 10:48 PM

[nuhi]

If I knew what it was I would fix it.

To me it's all fine because I don't use SFC nor I see any benefit from it.

I gave you all the list what triggers patching, so either avoid that or turn off SFC.

[Madhits45]

I dont use SFC either. I always apply your patch to stop that annoying feature so I know its not windows replacing the file back or anything like that.

Also there is no way I could not use component removal. As for the rest of the triggers the only other one I use is some of the patches for TCP/IP and SFC.

It might be something Im doing thats causing the problem Ill have to strip my disc off all my reg entries and other customizations to narrow it down.

THANKS for your help though.

If anyone else has this problem in 2003 can you please explain the situation and what if anything you did to fix it?

[chiefnuts]

nuhi, on Sep 28 2007, 11:55 AM, said:

Madhits45,
how is it possible that that the line (movex syssbck ...) is missing from your nlite.inf?
Maybe you think that I should know that but it simply seems not possible, even though I hope that's the case and we find out why.

Do you (all with this issue of not having the restored file) run Windows by setup.exe (winnt32.exe) or use your own winnt.sif file or anything that would skip this portion?

Because by just using nLite with it's Unattended options should be fine.

I'm having this problem with XP SP2 VLK media. I slipstream the patches and then several drivers (SATA) into the build. I don't delete CAT files, but my nlite.inf was missing the movex syssbck command, as well as the syssbck file. Does this apply to me as well? Just so you know, the whole process works fine untill I plug in a USB mouse or keyboard, and then windows prompts for the drivers. I can click though without going to windows update, and it works just fine, but then when I plug the USB mouse into a different port, the same thing occurs. Are these issues releated to this? I could really use some help.

What I am doing is then importing the build sources into BDD2007 and using that to deploy them. I believe it creates sysprep and unattended file for deployment.

CN

Addition: Replacing the file with the origonal corrects the issue. I just want to know why syssbck.dl_ isn't located in the build. Do i just need to try it again?

This post has been edited by chiefnuts: 19 November 2007 - 04:04 PM

[chiefnuts]

So here is what I found. I ran several tests slipstreaming the hotfixes into a SP2 VLK disk, and everytime I did so, I wouldn't get the syssbck.dl_ file on the system. I was building on a S23k ENT SP2 R2 build, and once I did the slipstreaming on a XP SP2 Machine, the files are now there. I'm going to test to make sure that this works correctly, but I don't see an issue now that the entries are correct.

Thanks,

CN

This post has been edited by chiefnuts: 20 November 2007 - 02:23 PM

[chiefnuts]

Ok, I got it to work once, but now I cannot get it to create the syssbck.dl_ & syssbck.in_ files. Is there something I'm missing? I'm integrating just drivers and Patches (SATA drivers only) but it doesn't recreate the sysbck.dll file. Do I need to make changes in other locations on the machine? Please help