“Windows Setup could not configure Windows on this computer’s hardware” installation error on a Windows 7-based or a Windows Server 2008 R2-based computer.     

SYMPTOMS

When you perform a clean installation of Windows 7 or of Windows Server 2008 R2, you may receive the following error message during the device-detection phase of setup:

Windows Setup could not configure Windows on this computer’s hardware.

This error can occur when you try to install Windows 7 or Windows Server 2008 R2 on a system if the following situation is true on your PC:

• You are installing by using Windows 7 or Windows Server 2008 R2 RTM media. 
  
  Note: Windows 7 with Service Pack 1 (SP1) and Windows Server 2008 R2 with SP1 are not affected by this issue.
• Your system has an Intel storage controller that is configured to "RAID" mode in the BIOS. (This is a standard setting for many PC manufacturers)
• The hard drive you are installing to ia an "Advanced Format" disk.
  
  Note Advanced Format disks have a physical sector size of 4 kilobytes and a logical emulated sector size of 512 bytes. "Advanced Format" is a new technology being adopted by PC manufacturers to increase media format efficiency which will lead to larger capacity hard drives. If you are replacing a hard drive in an older PC, you may be more likely to encounter this issue.

How do I know if I have this issue?

To determine whether your system is affected by this issue, follow these steps:

1. Insert a Windows 7 or Windows Server 2008 R2 DVD into your DVD drive, and then close the drive.
2. Restart your computer, and then press a key on the keyboard when you receive the following message:
   
   Press any key to boot from CD or DVD
3. Set the following preferences, and then click Next.
   • Language to install
   • Time and currency format
   • Keyboard or input method
4. On the next screen, select Repair your computer.
5. In the System Recover Option dialog box, select the drive that you tried to install Windows 7 or Windows Server 2008 R2.
6. In the Choose a Recovery Tool box, select Command Prompt.
7. Change to the drive that you want to install Windows on. (In a standard installation, this is drive C.) Type Notepad, and then press ENTER.
8. In Notepad, click Open on the File menu, and then browse to %systemroot%\Panther.
   
   Note On a standard installation to drive C, the path is C:\Windows\Panther. (On most PCs this will be the C:\Panther folder)
9. Open the file setuperr.log, and look for lines that resemble these:
   
   2010-09-23 17:34:58, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\scecli.dll,SceSysPrep', returned error code 1208[gle=0x000003e5]
   2010-09-23 17:34:59, Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x4b8
   
   Note If these lines and errors exist, note the errors.
10. Open the setupact.log file that is located in the same directory, and then look for the line that resembles the following line:
    
    2010-09-23 17:31:26, Info SYSPRP SPPNP: iaStorV is the function driver for device PCI\VEN_8086&DEV_2822&SUBSYS_2819103C&REV_02\3&33FD14CA&0&FA
    
    Note If this line exists, it indicates that the drive on which you are trying to install Windows 7 or Windows Server 2008 R2 is configured in a RAID configuration.

CAUSE

This error occurs because of an issue with the Intel storage controller driver that's included in the released versions of Windows 7 and of Windows Server 2008 R2. This issue is resolved in Windows 7 SP1 and in Windows Server 2008 R2 SP1.

RESOLUTION

To help resolve this issue and install Windows 7 or Windows Server 2008 R2 on your computer, follow these steps. Method 1 is the easiest and preferred method. If you cannot complete method 1, try method 2.

Method 1: Download the appropriate drivers for your hard disk drive

Download and install the latest drivers for your Windows 7-based or Windows Server 2008 R2-based computer. To do this by using another computer, visit the following Intel website and download the appropriate drivers for your hard disk drive (either 32-bit or 64-bit) to a flash drive. Or, burn the drivers onto a CD or DVD. The flash drive or the disc will then be used during setup of Windows 7 or of Windows Server 2008 R2.

http://www.intel.com/support/chipsets/imsm/sb/CS-031502.htm

1. Go to another computer that has an internet connection and click the link below to download the driver for your hard disk drive (either 32-bit or 64-bit):
   
   http://www.intel.com/support/chipsets/imsm/sb/CS-031502.htm
2. Save this downloaded driver to a DVD or USB flash drive or an external hard drive that can be taken to the PC that you're installing Windows to. 
3. Next, start the installation of Windows 7 or Windows Server 2008 R2 and watch for the Load Driver option. You will see this option on the Where do you want to install Windows? screen in the lower right corner.
4. Connect the USB flash or external drive to the computer that you're installing Windows or take the Windows DVD out of the drive and put the driver DVD into the drive. (You will put the Windows DVD back into that drive after the driver is loaded)
5. Click Load Driver, (clicking this option checks removable media for storage controller drivers) 
6. Once the driver is loaded, continue with the Windows setup.

The Advanced Drive Format hard drive will be recognized and Setup will continue as expected.

Method 2: Change the BIOS hard disk drive setting to AHCI or IDE

Warning This procedure may involve changing your hard disk drive settings in the BIOS. Incorrect changes to the BIOS of your computer can result in serious problems. Microsoft cannot guarantee that problems that result from changes to the BIOS can be resolved. Change the BIOS settings at your own risk. Incorrect or corrupted BIOS settings can cause startup problems or shutdown problems.

You can change the hard disk drive setting in the BIOS to AHCI or to IDE if the hard disk drive setting is currently set to a RAID configuration. If you set the hard disk drive to AHCI or to IDE, you do not have to install the driver that you obtained in method 1.

Microsoft cannot provide specific instructions for how to change the BIOS settings because they are specific to your computer. For information about the correct BIOS settings for your computer and how to check and change these settings, see your computer documentation, or contact the manufacturer of your computer.

MORE INFORMATION

For more information about Windows 7 and Windows Server 2008 R2 compatibility with Advanced Format disks, click the following article number to view the article in the Microsoft Knowledge Base:

982018 An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

             Properties

Article ID: 2466753 - Last Review: 01/20/2012 20:22:00 - Revision: 3.0

Applies to

• Windows 7 Starter
• Windows 7 Home Basic
• Windows 7 Home Premium
• Windows 7 Enterprise
• Windows 7 Professional
• Windows 7 Ultimate
• Windows Server 2008 R2 Standard
• Windows Server 2008 R2 Foundation
• Windows Server 2008 R2 Datacenter
• Windows Server 2008 R2 Enterprise

Keywords:

• KB2466753.          

SQL Server Installation Rules and “System Reboot Required” Error

SQL Server Installation Rules and “System Reboot Required” Error

When we do installation or removing SQL Server, it always executes installation rules. And what really weird is, installer even checks for these rules when we want to Un-install the SQL Server (kind of reminds me, my experience with Office ‘97 which had quite similar craving for installation media while uninstalling).

Today, when we were trying to install SQL server on one of our test machine which was built freshly from scratch was acting really weird. When I ran the installation, it executed installation rules as usual to check if there is something missing. But I got this common error saying “RebootRequiredCheck: Failed”, which basically says that System Reboot is Required, so we thought it might be because of some update (Windows does have really bad habit of asking to reboot every now and then after updates ). So we did as required by SQL Server and rebooted the system. Then we again fired the installation process and guess what ?? we had again same error !! We tried couple of other stuffs like cleaning temp files and stopping services which might be causing this problem but it didn’t worked even after 3-4 reboots. So, finally wise guy (me ) thought to Google this problem, and I found that this error has nothing to do with SQL Server itself !!

Actually it is because of Windows … apparently, when there is some updates are done or some critical software is installed, windows sets a parameter in registry which makes that windows gets rebooted once that process is completed. But somehow, that registry value doesn’t get reset even after reboot and that can cause trouble for SQL Server !! So, we have to manually remove that value from registry.

I followed the following steps to solve this problem,
1. Fire Regedit.exe application in Windows.
2. Go to, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager , and instead of “EXPANDING” Session Manager, “SELECT” it and you will see the entry called, PENDING FILE RENAME OPERATION.
3. Take backup of registry value first.
4. Then, If PENDING FILE RENAME OPERATION has any values just remove it and clear the value.
5. Reboot the System and again go to PENDING FILE RENAME OPERATION and see if there is any values still available.
6. If no value is there then simply fire the installation process.
7. If any value is still present then simply remove that value and without restarting fire the installation process.
And after this everything went super smooth for us (or say for me ).

Actually there are some other causes of this type of error too. To be honest, surprisingly I found only one post to the point this specific error and I have included link over there, which has some other causes that can make SQL Server installer to generate same error.

Framwork 1.1 installation in Windows 7

This has been known forever, from Vista through to Windows 7.

1. Create a new folder named DotNet in C:\ drive (C:\DotNet is used in this guide, you can change to any folder you prefer, but ensure that you use correct path in the following steps).
2. Download Microsoft .NET Framework 1.1 Redistributable Package (dotnetfx.exe ). Make sure the setup file is saved as dotnetfx.exe .
3. Download Microsoft .NET Framework 1.1 Service Pack 1 (NDP1.1sp1-KB867460-X86.exe ). Make sure that the file is renamed and saved as dotnetfxsp1.exe , so that the rest of the steps can be followed easily.
4. Move both installation files into the same directory (i.e. C:\DotNet), if you’re not saving them together.
5. Open command prompt as Administrator .
6. Change to the directory where the two installation setup files for .NET 1.1 are saved (i.e. C:\DotNet).
7. Run the following commands one by one, press Enter after each one.
• dotnetfx.exe /c:"msiexec.exe /a netfx.msi TARGETDIR=C:\DotNet"
• Then click on “Yes” when prompted to answer “would you like to install Microsoft .NET Framework 1.1. Package?”
• dotnetfxsp1.exe /Xp:C:\DotNet\netfxsp.msp
• msiexec.exe /a c:\DotNet\netfx.msi /p c:\DotNet\netfxsp.msp

Install Microsoft .Net Framework 1.1 with slipstreamed/integrated Service Pack 1 by running netfx.msi created in the working folder.

Server is not accessible You might not have permission to use this network resource

Server is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Some time you cannot accessible the particular Server / Computer. At the mean time you can able to access other Servers / Computers. When trying to accessing you will get following error...


---------------------------
Windows Explorer
---------------------------
\\vss is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The user name could not be found.
---------------------------
OK 
---------------------------



Reason of an Issue:

You was changed domain / user's login. Also you was saved Path, Username and Password when previous accessing time. Due to this reason, when you trying to access,  it will search previously saved Path and Login details. So it was omitting error like that.

Solutions:

Go to Control Panel → and find User Accounts



Open User Accounts



Select Advanced tab



Click Manage Passwords and click the Remove button.

Then close it and try to access.

Enjoy!!!