I found the solution to this problem today. Just as you got no answer here I haven't seen anyone else pinpoint the cause yet. Basically the SSD doesn't have a boot sector so Windows installs it's boot sector to the first available mechanical drive. If you leave the Windows disk in, you'll notice that if you ignore the "press any key to boot from cd" prompt the boot loader on the cd will load Windows from your SSD. The problem is logically when you go to install a new hard drive with a fresh OS you probably went into BIOS and set the SSD as the first bootable hard drive. Windows put the boot loader on the first bootable mechanical drive (the second bootable hard drive) so your pooch was screwed. If you go into BIOS and move the SSD down the boot order by one drive you should be able to boot into Windows normally.
If this helps, please go to the blog post I wrote about this problem at the link below and click on the google ad at the top so I can earn a few cents.
http://web.archive.org/web/20140417212549/http://suffolk757.com/?p=290
Finally I've got a working solution, based on this tweet:
- Disable all antivirus tools (I've had no external tools beside the Windows-built-in, so nothing to do here for me).
- Follow the instructions in the KB article.
The KB article shows a script to run, after installing a MSI.
I've had to adjust the script since the Windows user group account administrators is named administratoren in my German Windows 8.1.
After running the adjusted script (for about 10-20 minutes), I've launched the Windows 10 setup again and it ran k.
I'm now writing this from my Windows 10 and seem to be happy.
Update
Since the Microsoft KB article seems to be removed, I've opened the Google Cache version of the KB article and copying the relevant information here.
From the KB article:
Error 0x80070005 in Windows Update when you try to install updates
Resolution
Error code 0x80070005 is also known as "ACCESS DENIED." It usually occurs when you lack file or registry permissions that are required to install the update. (Because file or registry permissions may be changed by malware, we recommend that you scan for malware after you repair the permissions.)
To resolve the issue, make sure that you are logged on as an administrator, and then install the updates again. If the problem continues, use the SubInACL tool to repair file and registry permissions. To do this, follow these steps:
Download the SubInACL tool (Mirror), and install it to the default path that is offered by the installer. The default path will be one of the following, depending on your version of Windows:
- %ProgramFiles%\Windows Resource Kits\Tools (32-bit versions of Windows)
- %ProgramFiles(x86)%\Windows Resource Kits\Tools (64-bit versions of Windows)
Start Notepad, and then copy and paste the following commands:
@echo off
setlocal
echo.
echo Determine whether we are on an 32 or 64 bit machine
echo.
if "%PROCESSOR_ARCHITECTURE%"=="x86" if "%PROCESSOR_ARCHITEW6432%"=="" goto x86
set ProgramFilesPath=%ProgramFiles(x86)%
goto startResetting
:x86
set ProgramFilesPath=%ProgramFiles%
:startResetting
echo.
if exist "%ProgramFilesPath%\Windows Resource Kits\Tools\subinacl.exe" goto filesExist
echo ***ERROR*** - Could not find file %ProgramFilesPath%\Windows Resource Kits\Tools\subinacl.exe. Double-check that SubInAcl is correctly installed and re-run this script.
goto END
:filesExist
pushd "%ProgramFilesPath%\Windows Resource Kits\Tools"
subinacl.exe /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f
subinacl.exe /subkeyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f
subinacl.exe /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f
subinacl.exe /subdirectories %windir% /grant=administrators=f /grant=system=f
echo FINISHED.
echo.
echo Press any key to exit . . .
pause >NUL
popd
:END
endlocal
Save the file as Reset.cmd. (Super User note: English download, German download)
- Right-click the Reset.cmd file in File Explorer (in Windows 8.1 and Windows 8) or Windows Explorer (in Windows 7 and Windows Vista), and then click Run as administrator. In Windows XP, double-click the file in Windows Explorer.
- Wait until the execution finishes, and then try to install the update again.
Note If you receive errors when you run SubInAcl, see the following Microsoft blog: Notes about a couple of possible issues while using the SubInAcl tool.
Best Answer
Windows XP does not have built in drivers to recognize SATA drives. You need a floppy disk containing said drivers or slipstream them into the installation media. Google can help you.
If that isn't the issue (i.e. you already have drivers) then it's probably a keyboard issue, as already stateed here, or memory, or the installation media is scratched/broken.