setupapi logs

NTDEV
1

I have a vista32 on x86
I have a network card which came with in the box drivers.

I replaced the ITB with the driver from the vendor site, all went well and
the device works. Since it is a NIC so no restart required also.

Now I update this driver with a vendor upgrade (both INF name and driver
name same). Installer through INF completes, and this time vista asks for a
reboot. Note that device vendor says that the driver works just fine, i
already checked.

The device comes with coinstallers. Driver is not signed, so not catlog
file.

I dig into setupapi.dev file in c:\windows and see setup to throw some
errors but I dont know if these are significant enough. Am pasting only the
error lines, as the log is too large to paste. Any clues? Is vista simply
being finnicky? one possibility could be that at first time replacement when
ITB is replaped there is no repository entry (the ITB INF is different name
so is the binary), so when we replace it with vendor one, the repo gets
created, and next time on update it causes an issue.

{DIF_UPDATEDRIVER_UI - exit(0xe000020e)}
{DIF_SELECTDEVICE - exit(0xe000020e)}
{DIF_SELECTDEVICE - exit(0xe000020e)}
{_VERIFY_FILE_SIGNATURE exit(0x00000057)}
{_VERIFY_FILE_SIGNATURE exit(0x80092003)}
{_VERIFY_FILE_SIGNATURE exit(0x00000057)}
{_VERIFY_FILE_SIGNATURE exit(0x80092003)}
{DIF_ALLOW_INSTALL - exit(0xe000020e)}
{SPFILENOTIFY_STARTCOPY - exit(0x00000001)}

2

Look in %windir%\inf\setupapi.dev.log as well

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 6:56 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] setupapi logs

I have a vista32 on x86

I have a network card which came with in the box drivers.

I replaced the ITB with the driver from the vendor site, all went well
and the device works. Since it is a NIC so no restart required also.

Now I update this driver with a vendor upgrade (both INF name and driver
name same). Installer through INF completes, and this time vista asks
for a reboot. Note that device vendor says that the driver works just
fine, i already checked.

The device comes with coinstallers. Driver is not signed, so not catlog
file.

I dig into setupapi.dev file in c:\windows and see setup to throw some
errors but I dont know if these are significant enough. Am pasting only
the error lines, as the log is too large to paste. Any clues? Is vista
simply being finnicky? one possibility could be that at first time
replacement when ITB is replaped there is no repository entry (the ITB
INF is different name so is the binary), so when we replace it with
vendor one, the repo gets created, and next time on update it causes an
issue.

{DIF_UPDATEDRIVER_UI - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{DIF_ALLOW_INSTALL - exit(0xe000020e)}

{SPFILENOTIFY_STARTCOPY - exit(0x00000001)}

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

doron,

excuse my ignorance. but what are the different setupapi log files in the
different folders for?

bed

On 7/2/07, Doron Holan wrote:
>
> Look in %windir%\inf\setupapi.dev.log as well
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 6:56 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] setupapi logs
>
>
>
> I have a vista32 on x86
>
> I have a network card which came with in the box drivers.
>
>
>
> I replaced the ITB with the driver from the vendor site, all went well and
> the device works. Since it is a NIC so no restart required also.
>
>
>
> Now I update this driver with a vendor upgrade (both INF name and driver
> name same). Installer through INF completes, and this time vista asks for a
> reboot. Note that device vendor says that the driver works just fine, i
> already checked.
>
>
>
>
>
> The device comes with coinstallers. Driver is not signed, so not catlog
> file.
>
>
>
> I dig into setupapi.dev file in c:\windows and see setup to throw some
> errors but I dont know if these are significant enough. Am pasting only the
> error lines, as the log is too large to paste. Any clues? Is vista simply
> being finnicky? one possibility could be that at first time replacement when
> ITB is replaped there is no repository entry (the ITB INF is different name
> so is the binary), so when we replace it with vendor one, the repo gets
> created, and next time on update it causes an issue.
>
>
>
>
>
> {DIF_UPDATEDRIVER_UI - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {DIF_ALLOW_INSTALL - exit(0xe000020e)}
>
> {SPFILENOTIFY_STARTCOPY - exit(0x00000001)}
>
> — Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
> Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

4

There was a lot of cleanup done in vista with respect to the setup logs,
a lot of what used to be in %windir%\setupapi.log is now in the log I
mentioned. Did you look in the log to see what was there?

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 10:00 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] setupapi logs

doron,

excuse my ignorance. but what are the different setupapi log files in
the different folders for?

bed

On 7/2/07, Doron Holan wrote:

Look in %windir%\inf\setupapi.dev.log as well

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 6:56 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] setupapi logs

I have a vista32 on x86

I have a network card which came with in the box drivers.

I replaced the ITB with the driver from the vendor site, all went well
and the device works. Since it is a NIC so no restart required also.

Now I update this driver with a vendor upgrade (both INF name and driver
name same). Installer through INF completes, and this time vista asks
for a reboot. Note that device vendor says that the driver works just
fine, i already checked.

The device comes with coinstallers. Driver is not signed, so not catlog
file.

I dig into setupapi.dev file in c:\windows and see setup to throw some
errors but I dont know if these are significant enough. Am pasting only
the error lines, as the log is too large to paste. Any clues? Is vista
simply being finnicky? one possibility could be that at first time
replacement when ITB is replaped there is no repository entry (the ITB
INF is different name so is the binary), so when we replace it with
vendor one, the repo gets created, and next time on update it causes an
issue.

{DIF_UPDATEDRIVER_UI - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{DIF_ALLOW_INSTALL - exit(0xe000020e)}

{SPFILENOTIFY_STARTCOPY - exit(0x00000001)}

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

5

in my case i see them identical.

The issue seems here to be that the coinstaller cannot be over written, and
hence windows tries a reboot to overwrite it. Could it be an uninstall
problem, where the installer is not releasing teh DLL properly?

On 7/2/07, Doron Holan wrote:
>
> There was a lot of cleanup done in vista with respect to the setup logs,
> a lot of what used to be in %windir%\setupapi.log is now in the log I
> mentioned. Did you look in the log to see what was there?
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 10:00 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] setupapi logs
>
>
>
> doron,
>
>
>
> excuse my ignorance. but what are the different setupapi log files in the
> different folders for?
>
>
>
> bed
>
>
>
>
>
>
>
>
>
> On 7/2/07, Doron Holan wrote:
>
> Look in %windir%\inf\setupapi.dev.log as well
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 6:56 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] setupapi logs
>
>
>
> I have a vista32 on x86
>
> I have a network card which came with in the box drivers.
>
>
>
> I replaced the ITB with the driver from the vendor site, all went well and
> the device works. Since it is a NIC so no restart required also.
>
>
>
> Now I update this driver with a vendor upgrade (both INF name and driver
> name same). Installer through INF completes, and this time vista asks for a
> reboot. Note that device vendor says that the driver works just fine, i
> already checked.
>
>
>
>
>
> The device comes with coinstallers. Driver is not signed, so not catlog
> file.
>
>
>
> I dig into setupapi.dev file in c:\windows and see setup to throw some
> errors but I dont know if these are significant enough. Am pasting only the
> error lines, as the log is too large to paste. Any clues? Is vista simply
> being finnicky? one possibility could be that at first time replacement when
> ITB is replaped there is no repository entry (the ITB INF is different name
> so is the binary), so when we replace it with vendor one, the repo gets
> created, and next time on update it causes an issue.
>
>
>
>
>
> {DIF_UPDATEDRIVER_UI - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {DIF_ALLOW_INSTALL - exit(0xe000020e)}
>
> {SPFILENOTIFY_STARTCOPY - exit(0x00000001)}
>
> — Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> — Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
> Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

6

This is a known limitation of coinstallers since win2k. If you are
updating coinstaller with a binary of the same name, you will always
need to reboot b/c the coinstaller being replaced is loaded and in use
by setup for the entire remove operation.

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 12:42 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] setupapi logs

in my case i see them identical.

The issue seems here to be that the coinstaller cannot be over written,
and hence windows tries a reboot to overwrite it. Could it be an
uninstall problem, where the installer is not releasing teh DLL
properly?

On 7/2/07, Doron Holan wrote:

There was a lot of cleanup done in vista with respect to the setup logs,
a lot of what used to be in %windir%\setupapi.log is now in the log I
mentioned. Did you look in the log to see what was there?

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 10:00 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] setupapi logs

doron,

excuse my ignorance. but what are the different setupapi log files in
the different folders for?

bed

On 7/2/07, Doron Holan wrote:

Look in %windir%\inf\setupapi.dev.log as well

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 6:56 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] setupapi logs

I have a vista32 on x86

I have a network card which came with in the box drivers.

I replaced the ITB with the driver from the vendor site, all went well
and the device works. Since it is a NIC so no restart required also.

Now I update this driver with a vendor upgrade (both INF name and driver
name same). Installer through INF completes, and this time vista asks
for a reboot. Note that device vendor says that the driver works just
fine, i already checked.

The device comes with coinstallers. Driver is not signed, so not catlog
file.

I dig into setupapi.dev file in c:\windows and see setup to throw some
errors but I dont know if these are significant enough. Am pasting only
the error lines, as the log is too large to paste. Any clues? Is vista
simply being finnicky? one possibility could be that at first time
replacement when ITB is replaped there is no repository entry (the ITB
INF is different name so is the binary), so when we replace it with
vendor one, the repo gets created, and next time on update it causes an
issue.

{DIF_UPDATEDRIVER_UI - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{DIF_ALLOW_INSTALL - exit(0xe000020e)}

{SPFILENOTIFY_STARTCOPY - exit(0x00000001)}

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

7

oooooooooooh :open_mouth: :open_mouth: really.

  1. So is there a work around?
  2. Sir, is there a document where I can read abt it more this issue
    specifically?

bed

On 7/3/07, Doron Holan wrote:
>
> This is a known limitation of coinstallers since win2k. If you are
> updating coinstaller with a binary of the same name, you will always need to
> reboot b/c the coinstaller being replaced is loaded and in use by setup for
> the entire remove operation.
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 12:42 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] setupapi logs
>
>
>
> in my case i see them identical.
>
>
>
> The issue seems here to be that the coinstaller cannot be over written,
> and hence windows tries a reboot to overwrite it. Could it be an uninstall
> problem, where the installer is not releasing teh DLL properly?
>
>
>
>
>
>
>
> On 7/2/07, Doron Holan wrote:
>
> There was a lot of cleanup done in vista with respect to the setup logs, a
> lot of what used to be in %windir%\setupapi.log is now in the log I
> mentioned. Did you look in the log to see what was there?
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 10:00 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] setupapi logs
>
>
>
> doron,
>
>
>
> excuse my ignorance. but what are the different setupapi log files in the
> different folders for?
>
>
>
> bed
>
>
>
>
>
>
>
>
>
> On 7/2/07, Doron Holan wrote:
>
> Look in %windir%\inf\setupapi.dev.log as well
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 6:56 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] setupapi logs
>
>
>
> I have a vista32 on x86
>
> I have a network card which came with in the box drivers.
>
>
>
> I replaced the ITB with the driver from the vendor site, all went well and
> the device works. Since it is a NIC so no restart required also.
>
>
>
> Now I update this driver with a vendor upgrade (both INF name and driver
> name same). Installer through INF completes, and this time vista asks for a
> reboot. Note that device vendor says that the driver works just fine, i
> already checked.
>
>
>
>
>
> The device comes with coinstallers. Driver is not signed, so not catlog
> file.
>
>
>
> I dig into setupapi.dev file in c:\windows and see setup to throw some
> errors but I dont know if these are significant enough. Am pasting only the
> error lines, as the log is too large to paste. Any clues? Is vista simply
> being finnicky? one possibility could be that at first time replacement when
> ITB is replaped there is no repository entry (the ITB INF is different name
> so is the binary), so when we replace it with vendor one, the repo gets
> created, and next time on update it causes an issue.
>
>
>
>
>
> {DIF_UPDATEDRIVER_UI - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {DIF_ALLOW_INSTALL - exit(0xe000020e)}
>
> {SPFILENOTIFY_STARTCOPY - exit(0x00000001)}
>
> — Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> — Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> — Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
> Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

8

The only workaround is to give your coinstaller a new name, there is no
workaround for servicing a coinstaller with the same name. I don’t
think there is a doc on this, I can ask the DMI guys though.

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 1:54 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] setupapi logs

oooooooooooh :open_mouth: :open_mouth: really.

  1. So is there a work around?

  2. Sir, is there a document where I can read abt it more this issue
    specifically?

bed

On 7/3/07, Doron Holan wrote:

This is a known limitation of coinstallers since win2k. If you are
updating coinstaller with a binary of the same name, you will always
need to reboot b/c the coinstaller being replaced is loaded and in use
by setup for the entire remove operation.

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 12:42 PM

To: Windows System Software Devs Interest List
Subject: Re: [ntdev] setupapi logs

in my case i see them identical.

The issue seems here to be that the coinstaller cannot be over written,
and hence windows tries a reboot to overwrite it. Could it be an
uninstall problem, where the installer is not releasing teh DLL
properly?

On 7/2/07, Doron Holan wrote:

There was a lot of cleanup done in vista with respect to the setup logs,
a lot of what used to be in %windir%\setupapi.log is now in the log I
mentioned. Did you look in the log to see what was there?

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 10:00 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] setupapi logs

doron,

excuse my ignorance. but what are the different setupapi log files in
the different folders for?

bed

On 7/2/07, Doron Holan wrote:

Look in %windir%\inf\setupapi.dev.log as well

d

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Monday, July 02, 2007 6:56 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] setupapi logs

I have a vista32 on x86

I have a network card which came with in the box drivers.

I replaced the ITB with the driver from the vendor site, all went well
and the device works. Since it is a NIC so no restart required also.

Now I update this driver with a vendor upgrade (both INF name and driver
name same). Installer through INF completes, and this time vista asks
for a reboot. Note that device vendor says that the driver works just
fine, i already checked.

The device comes with coinstallers. Driver is not signed, so not catlog
file.

I dig into setupapi.dev file in c:\windows and see setup to throw some
errors but I dont know if these are significant enough. Am pasting only
the error lines, as the log is too large to paste. Any clues? Is vista
simply being finnicky? one possibility could be that at first time
replacement when ITB is replaped there is no repository entry (the ITB
INF is different name so is the binary), so when we replace it with
vendor one, the repo gets created, and next time on update it causes an
issue.

{DIF_UPDATEDRIVER_UI - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{DIF_SELECTDEVICE - exit(0xe000020e)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{_VERIFY_FILE_SIGNATURE exit(0x00000057)}

{_VERIFY_FILE_SIGNATURE exit(0x80092003)}

{DIF_ALLOW_INSTALL - exit(0xe000020e)}

{SPFILENOTIFY_STARTCOPY - exit(0x00000001)}

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

9

had a chat with the devs here abt this. They say (as u suggested) that the
rename workaround was in place, but REMOVED, as they they believed this
issue was FIXED in Vista. Now that you confirm that vista still has the same
problem, I guess we have to put it back.

Can you also please ask the DMI guys as u suggested. It would be of help.

bed

On 7/3/07, Doron Holan wrote:
>
> The only workaround is to give your coinstaller a new name, there is no
> workaround for servicing a coinstaller with the same name. I don’t think
> there is a doc on this, I can ask the DMI guys though.
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 1:54 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] setupapi logs
>
>
>
> oooooooooooh :open_mouth: :open_mouth: really.
>
>
>
> 1. So is there a work around?
>
> 2. Sir, is there a document where I can read abt it more this issue
> specifically?
>
>
>
>
>
> bed
>
>
>
> On 7/3/07, Doron Holan wrote:
>
> This is a known limitation of coinstallers since win2k. If you are
> updating coinstaller with a binary of the same name, you will always need to
> reboot b/c the coinstaller being replaced is loaded and in use by setup for
> the entire remove operation.
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 12:42 PM
>
>
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] setupapi logs
>
>
>
> in my case i see them identical.
>
>
>
> The issue seems here to be that the coinstaller cannot be over written,
> and hence windows tries a reboot to overwrite it. Could it be an uninstall
> problem, where the installer is not releasing teh DLL properly?
>
>
>
>
>
>
>
> On 7/2/07, Doron Holan wrote:
>
> There was a lot of cleanup done in vista with respect to the setup logs, a
> lot of what used to be in %windir%\setupapi.log is now in the log I
> mentioned. Did you look in the log to see what was there?
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 10:00 AM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] setupapi logs
>
>
>
> doron,
>
>
>
> excuse my ignorance. but what are the different setupapi log files in the
> different folders for?
>
>
>
> bed
>
>
>
>
>
>
>
>
>
> On 7/2/07, Doron Holan wrote:
>
> Look in %windir%\inf\setupapi.dev.log as well
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com [mailto:
> xxxxx@lists.osr.com] *On Behalf Of *Bedanto
> Sent: Monday, July 02, 2007 6:56 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] setupapi logs
>
>
>
> I have a vista32 on x86
>
> I have a network card which came with in the box drivers.
>
>
>
> I replaced the ITB with the driver from the vendor site, all went well and
> the device works. Since it is a NIC so no restart required also.
>
>
>
> Now I update this driver with a vendor upgrade (both INF name and driver
> name same). Installer through INF completes, and this time vista asks for a
> reboot. Note that device vendor says that the driver works just fine, i
> already checked.
>
>
>
>
>
> The device comes with coinstallers. Driver is not signed, so not catlog
> file.
>
>
>
> I dig into setupapi.dev file in c:\windows and see setup to throw some
> errors but I dont know if these are significant enough. Am pasting only the
> error lines, as the log is too large to paste. Any clues? Is vista simply
> being finnicky? one possibility could be that at first time replacement when
> ITB is replaped there is no repository entry (the ITB INF is different name
> so is the binary), so when we replace it with vendor one, the repo gets
> created, and next time on update it causes an issue.
>
>
>
>
>
> {DIF_UPDATEDRIVER_UI - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {DIF_SELECTDEVICE - exit(0xe000020e)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x00000057)}
>
> {_VERIFY_FILE_SIGNATURE exit(0x80092003)}
>
> {DIF_ALLOW_INSTALL - exit(0xe000020e)}
>
> {SPFILENOTIFY_STARTCOPY - exit(0x00000001)}
>
> — Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> — Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> — Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> — Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
> Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>