Windows setup could not configure windows to run on this hardware message during repair install

Anonymous
2018-08-24T03:20:19+00:00

Windows 7 Ultimate SP1 x64

I am trying to do a repair install of Windows 7 Ultimate which came pre-installed on the system, but every time I run windows setup, it gets 99% done, and is at the completing setup phase and suddenly pops up with a message saying windows can not be run on my current hardware. Setup then does a rollback of widows. This is absolutely ridiculous.... I am attempting to reinstall the SAME version of windows that was already on the system! Windows 7 Ultimate has been on the system since the day it rolled off the factory assembly line. I have triple checked to make sure the image I am using to do a repair install is x64. I have checked to make sure the image is not corrupted by doing a test install on a fresh drive in another PC. that time I got as far as asking for the license key before I stopped (because I didn't have a license for that PC).  I did find a support article on the dell support site surprisingly enough (why not the M$ support site too?) that said to press shift+F10 and start c:\windows\system32\oobe\msoobe.exe manually. which I tried, but when I started msoobe manually, I got as far as the screen that askes me about default IE security settings, then the screen went almost black. anyone just seeing the screen might think that the backlight had just turned off. you could dimly see the dialogs on the scree showing, but not well enough to see what you could select. the only thing that was clearly visible, and proved that the backlight for the display was indeed still active, was the mouse cursor was still clear as day. I tried restarting my pc, hoping I could pick up where I left off, but windows setup did a rollback instead. I don't know if a recent update is causing this, or if it is caused by the damage to windows I am trying to repair. I have never ever, in all  my years of using windows encountered this message.  the fact that it appears to not have an error code associated with it makes it all that much harder to diagnose. what can I do?

Windows for home | Previous Windows versions | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

43 answers

Sort by: Oldest
  1. Anonymous
    2018-08-25T22:40:56+00:00

    I skipped the license as well, but to get there, I had to start MSOOBE.exe manually. and then after a few dialog screens the screen got super dimmed.

    I am looking at the logs that got left behind in 'C:$WINDOWS.~BT\Sources\Panther' particularly the setupact.log an setuperr.log files. I am not really sure what I am looking for, however. would you be willing to take a look at them slance310?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-08-25T23:51:13+00:00

    I think I found where the point in the logs where windows setup fails, and the entry matches what is listed in the linked M$ support article (link at bottom of this post), but the only problem is, this issue is supposed to be solved with SP1. also while my system does have an intel storage controller, it DOES NOT support RAID.

    2018-08-25 00:36:09, Error      [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\scecli.dll,SceSysPrep', returned error code 1208[gle=0x000003e5]

    2018-08-25 00:36:09, Info                  IBS    Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers

    2018-08-25 00:36:09, Info                  IBS    Callback_Specialize: Specialize return: [1208]

    2018-08-25 00:36:09, Error      [0x060435] IBS    Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x4b8

    2018-08-25 00:36:09, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not configure Windows to run on this computer's hardware.]

    https://support.microsoft.com/en-us/help/2466753/windows-setup-could-not-configure-windows-on-this-computer-s-hardware

    https://www.dell.com/support/article/gu/en/gubiz1/sln293812/-windows-setup-could-not-configure-to-run-on-this-computers-hardware-error-during-windows-7-or-windows-10-installation?lang=en

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-08-26T01:09:43+00:00

    Hi,

    Error logs are usually a bit over my head, but our Dell article mentions removing the installation media after running the MSOOBE.exe, and the installation should continue...

    Dell is also mentioning the command...

    Type cd c:\windows\system32\oobe and press Enter...

    I'm actually not sure if this is in reference to a physical CD\DVD drive, or something else...

    I'm wondering if you are running the repair from a extracted ISO, with a Virtual Drive, or a Flash Drive or something.. I ran the ISO with a Virtual drive..

    One thing you might try would be to reinstall the drivers for your Intel Chipset... The SATA Controller in particular...

    BTW... My machine has a second 3rd Party SATA Controller that needs it's own drivers..

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-08-28T22:55:56+00:00

    the fact that you do not have an intel controller could be the reason you did not run into the issue. according to the info I have found the issue seems to be exclusive to intel chipsets.

    I edited the registry to enable IDE mode. and then I switched the bios drive controller setting from AHCI to compatibility mode. when I restarted windows booted up and proceeded to install the IDE controller drivers. then when windows wanted to reboot again, things got a little strange. the bios would do it's POST check and hand things over to the OS to load, but instead of loading,  it just sat there, with a blinking text cursor in the far upper left corner. I restarted the PC about 5 or six times, and on the last time, windows started to load. Once windows was loaded, I ran windows setup. this time around, windows setup completed successfully but for some reason it took a really long time to complete. once windows was back running again, it started to do what it did before, i.e. that blank screen thing again. after a few restarts windows loaded. once I was in windows I switched the registry so that the SATA mode drivers would load and switched the bios back to AHCI. Windows then loaded on the first try. don't know why windows was balking at loading windows before, but what ever. On sunday/Monday I proceeded to let windows install all the updates.

    when I checked for updates oddly enough, windows 7 SP1 was listed. I check the system to be sure, and SP1 was indeed already installed. the update was only around 9.8Mb,o I'm not sure what that was about. despite my best intentions windows installed every update released since SP1 came out. A hotfix was also automatically installed, which is odd. the hotfix was kb2534111. also windows update did not list or install the two updates that comprise the so called SP2 "convenience rollup" update. I tried to install the fist of the two manually (KB3020369) but windows said the update was not applicable. I double check to make sure I was using the x64 version, but windows would not install it. I currently am trying to install the second part of the sp2 update. I don't know if I need these updates in order to receive the update rollups, but so far windows did not install any. and windows updates says windows is upto date.

    Windows is still acting a lttle squirrely but less so than before. the problem I tried to fix with the repair install also did not get fixed as I had hoped. (the IPv6 transition technologies had stopped working, disabling my ipv6 tunnel. also I am getting these error messages when I use ipconfig /renew6 or /release6:

    An error occurred while renewing interface Teredo Tunneling Pseudo-Interface : The system cannot find the file specified.

    An error occurred while renewing interface isatap.{5AFECDAA-F792-428F-AC54-7F502420E218} : The system cannot find the file specified.

    An error occurred while renewing interface Loopback Pseudo-Interface 1 : The system cannot find the file specified.

    I might try running windows repair (upgrade) setup one more time to see if that fixes things and to see if the error I ran into before happens again.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-08-29T01:27:42+00:00

    Hi,

    I do in fact have an Intel Chipset... I also have Asmedia chipsets for extra SATA 3 and USB 3.0...

    I may have a different model Intel Chipset though...

    I have seen that 9MB SP1 Update as well... I Hide it...

    I have previously installed the so called SP2 Convenience Rollup, but had problems afterwards and started over, reinstalling Win 7 SP1..

    I don't recall if I had any trouble with installing either one of them on not, but my machine did not like something that was installed...

    The Rollups started in 2016, so you should be seeing some unless the SP2 Rollup snuck in somehow.. Even then, there have been some since...

    If I remember correctly, there were something like 172 Windows Updates that were listed after I did the Repair\Upgrade installs... I didn't install any of them since it was just a test...

    I don't have a clue as to why you would need to switch from AHCI to IDE to get the Repair Install to work... Unless maybe you didn't have updated drivers or something...

    My machine is set to use AHCI... it is a requirement for my SSD to function, but again... I may have a different generation chipset...

    Was this answer helpful?

    0 comments No comments