This is actually a solution. I'm posting in case someone else runs into this problem.
I was experimenting with a trying to revive a dead PC. It was an old Pentium III running a legacy app that had a hard disk fail. I had a very old Ghost image but recent "data-only" backups.
Since I didn't have a PC to spare, I decided to try to Ghost the old image onto a VHD. I was successful--VHD mount by AppAssure was very helpful.
But booting the VM resulted in a BSOD. No problem I thought. A repair install using the XP Pro CD should get it going. It did. Successfully boots but lacked Integration Services. Able to login as the old local admin account.
Tried to install Integration Services as usual but part way through, after "...framework install" or "ustor...something" and during "guest services", I got a 1603 error code.
After much fussing around I found that deep in the log files in C:\Windows (look for the most recent ones), there was an error trying to create the directory: C:\program files\Hyper-V Integration Services". I was local admin and the folder permissions for C:\Program Files" explicitly had full control for the local admin account so I couldn't understand why there was a problem. Just on a lark, I gave "Everyone" full control over "C:\program files" and afterwards, re-running the Integration Services carried on to finish.
I'm too much of a noob to know what happened but I'm just reporting what I found was the solution.
- Changed type Vincent HuModerator Friday, September 24, 2010 6:45 AM
Other recent topics
