Vista - RE: Vista install problem - Failed to add driver package into driver s

Hello,
Upgrade or clean installation?
Are you adding drivers during setup or not adding drivers?
Is this a Retail or OEM installation?
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|>Thread-Topic: Vista install problem - Failed to add driver package into
driver s
|>thread-index: Acds33bloFyW8tF5TbOUamZXZnkMrQ==
|>X-WBNR-Posting-Host: 71.234.158.221
|>From: =?Utf-8?B?emlnbmVy?= <zigner@discussions.microsoft.com>
|>Subject: Vista install problem - Failed to add driver package into driver
s
|>Date: Thu, 22 Mar 2007 17:09:03 -0700
|>Lines: 45
|>Message-ID: <9DE574E0-95F6-4DB3-908D-0C66F0C8CE38@microsoft.com>
|>MIME-Version: 1.0
|>Content-Type: text/plain;
|> charset="Utf-8"
|>Content-Transfer-Encoding: 7bit
|>X-Newsreader: Microsoft CDO for Windows 2000
|>Content-Class: urn:content-classes:message
|>Importance: normal
|>Priority: normal
|>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
|>Newsgroups: microsoft.public.windows.vista.installation_setup
|>Path: TK2MSFTNGHUB02.phx.gbl
|>Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup:13361
|>NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
|>X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|>
|>Having a problem installing vista home premium. The following is from
the log:
|>
|>2007-03-22 19:58:35, Info [0x0602b0] IBS
|>AddDriverPackageIntoDriverStore:Successfully added the driver package
|>[C:\$WINDOWS.~BT\TempDriverStore\system32\DriverStore\FileRepository\ich8s
mb.inf_eae3c27f\ich8smb.inf]
|>into driver store. Destination driver package path is
|>[C:\$WINDOWS.~BT\Windows\system32\DriverStore\FileRepository\ich8smb.inf_e
ae3c27f\ich8smb.inf]
|>2007-03-22 19:58:35, Info [0x0602a8] IBS
|>CallBack_AddDriverPackageIntoDriverStore:Successfully installed the
driver
|>package
|>[C:\$WINDOWS.~BT\TempDriverStore\system32\DriverStore\FileRepository\ich8s
mb.inf_eae3c27f\ich8smb.inf].
|>Driver store path is
|>[C:\$WINDOWS.~BT\Windows\system32\DriverStore\FileRepository\ich8smb.inf_e
ae3c27f\ich8smb.inf]
|>2007-03-22 19:58:35, Info [0x0602a4] IBS
|>CallBack_AddDriverPackageIntoDriverStoreriver package path is
|>[C:\$WINDOWS.~BT\TempDriverStore\system32\DriverStore\FileRepository\ich8u
sb.inf_aacfb529\ich8usb.inf]
|>2007-03-22 19:58:35, Info [0x0602b2] IBS
|>CallBack_AddDriverPackageIntoDriverStoreriver package is [critical]
|>2007-03-22 19:58:35, Info IBS
|>AddDriverPackageIntoDriverStoreriver package path is
|>[C:\$WINDOWS.~BT\TempDriverStore\system32\DriverStore\FileRepository\ich8u
sb.inf_aacfb529\ich8usb.inf]
|>2007-03-22 19:58:35, Info IBS
|>AddDriverPackageIntoDriverStore:Image architecture is [0x0]
|>2007-03-22 19:58:35, Info IBS
|>AddDriverPackageIntoDriverStore:System root is [C:\$WINDOWS.~BT\Windows]
|>2007-03-22 19:58:35, Info IBS
|>AddDriverPackageIntoDriverStore:System drive is [X:\]
|>2007-03-22 19:58:35, Warning [0x0602b1] IBS
|>AddDriverPackageIntoDriverStore:Failed to add the driver package
|>[C:\$WINDOWS.~BT\TempDriverStore\system32\DriverStore\FileRepository\ich8u
sb.inf_aacfb529\ich8usb.inf] into driver store. Error code is [0x80070002]
|>2007-03-22 19:58:35, Error [0x0602a9] IBS
|>CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver
package
|>[C:\$WINDOWS.~BT\TempDriverStore\system32\DriverStore\FileRepository\ich8u
sb.inf_aacfb529\ich8usb.inf].
|>Driver package is [Critical]. Error code is [0x2][gle=0x00000002]
|>2007-03-22 19:58:35, Info [0x0640ae] IBSLIB PublishMessage:
Publishing
|>message [Windows installation cannot continue because a required driver
could
|>not be installed.]
|>2007-03-22 19:58:35, Info [0x0a013d] UI Accepting Cancel.
Exiting
|>Page Progress.
|>
|>
|>The error happens after a series of intel chipset drivers are
successfully
|>processed. All of them are in the same directory. Why would this one
give
|>such a problem?
|>
|>

Retail upgrade, clean install option. I decided to use all the latest
drivers included the Intel 965 drivers (which is where the problem seemed to
occur.