Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Problem deploying Windows Server 2008 R2 with Windows PE 4.0


  • Please log in to reply
2 replies to this topic

#1
confused_ka

confused_ka

    Newbie

  • Member
  • 11 posts
Hello,

I am using Windows PE 4.0 with built in powershell to deploy Windows Server 2008 R2. Basicly I am booting Windows PE 4.0 with all the neccessary drivers into the RAM Disk and from there on I get the unattended files and sources for Windows 2008 Server R2 and I will start the install process withhin the PE.

With Windows PE 3.1 I had 0 problems but now with PE 4.0 after the end of the Installation during the PE Part I get the following Error message "Installation cannot continue because a required driver could not be installed". Ofc I browsed thru the panther logs and found out it was the areca mass storage driver.

The logs are showing me this:

2013-01-11 15:15:49, Info [0x0a0024] UI progress task ProgressInfo\CBSServicing : EndProgress
2013-01-11 15:15:49, Info [0x0602a4] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package path is [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf]
2013-01-11 15:15:49, Info [0x0602b2] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package is [critical]
2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf]
2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x9]
2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:System root is [C:\Windows]
2013-01-11 15:15:49, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]
2013-01-11 15:16:11, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf] into driver store. Error code is [0x80070032]
2013-01-11 15:16:11, Error [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]
2013-01-11 15:16:11, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]
2013-01-11 15:16:11, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]

The driver itself works fine within the PE. Windows PE 4.0 can access the harddisks and the driver gets initialized properly. The same driver works with PE 3.1 and the unattended installation. I also tried to switch the driver with another version but still same error.

Anybody know what those error codes are standing for? Error code is [0x80070032] or Error code is [0x32][gle=0x00000032].

Regards,
Phil

Edited by confused_ka, 11 January 2013 - 10:47 AM.



How to remove advertisement from MSFN

#2
winoutreach5

winoutreach5

    Newbie

  • Member
  • 31 posts
  • OS:none specified
  • Country: Country Flag
The first step would be to ensure you are using the latest driver for the hardware and operating system. According to this page on the Areca Support and Downloads page for Windows, the latest Windows 8 / Windows Server 2012 drivers were released on December 21, 2012 for 32-bit and 64-bit architecture. I realize you are deploying Windows 2008R2 but as noted in the latest Windows PE Overview Windows PE 4.0 was built on the Windows 8 kernel. With that said, it may be experiencing compatibility issues with a driver that was written for Windows 7.

The next step would be to remove the driver in an effort to determine if the deployment is able to successfully complete without that driver in place. How are you launching Windows PE for deployment? Just to be safe, you might want to check out the Walkthrough: Install Windows PE to CD, USB Flash Drive, or USB Hard Drive library article on TechNet to ensure that a step wasn’t missed when creating the bootable Windows PE media. You will also want to ensure that you have created a new answer file using Windows SIM included in the Windows Automated Deployment Kit. This will ensure the new answer file is referencing the proper Windows PE version.

Finally, I always like to recommend the Deliver and Deploy page from the Springboard Series on TechNet as it offers several walkthrough videos, library articles and more that may provide additional insight into your current issue.

Jessica
Windows Outreach Team – IT Pro

#3
harkaz

harkaz

    Junior

  • Member
  • Pip
  • 74 posts
  • OS:Windows 7 x64
  • Country: Country Flag

2013-01-11 15:16:11, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf] into driver store. Error code is [0x80070032]
2013-01-11 15:16:11, Error [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [X:\windows\System32\DriverStore\FileRepository\oemsetup.inf_amd64_290ae086395dab44\oemsetup.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]
2013-01-11 15:16:11, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]
2013-01-11 15:16:11, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]


The problem is unsuccesful installation of driver in the driverstore. Try forcing unsigned driver installation when deploying with dism. If this does not fix the problem, then it is deeper and probably related to Windows 8 kernel, as stated in a previous answer.

Hope this helps




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN