This one will hang as unsolved. With the HD that successfully ran Sysprep to it's conclusion at a
machine shut down, I moved it to my other fully working system-- not the old one
I was trying to rejuvenate for a backup. That Sysprepped HD would not run the Setup
with the Installer disk in the DVD drive.
I'd ask again if anyone has actually seen this work and _if_ the motherboards have to
be similar as some Sysprep text has said? For me it was a no go.
Giving sysprep another whirl I had one question:
I have a successful sysprep shut down for the move to an MSI (newer) motherboard
this time to avoid any old board problems I might have missed previously.
The question is: Since Setup runs, does the System Setup disk need to be in the
dvd drive? It has to look for it's install items yes?
The MSI motherboard suite of drivers disk would then be run if I understand it correctly.
I will mark this solved when I reconnect and reboot to test.
What got past the errors was the helpful guide at this site:
Windows Clients - Its all about Microsoft Windows Client, Servers and much more
Follow the steps shown before running sysprep.
You will have to make your network connections and do some screen setup. Inspect your program
files and data files since you will have made a new user to initiate the procedure.
Sharma says you can revert to the original user afterward. That is another thing for me to test.
I had detached and replugged the sysprepped disk to test.
Bootmgr was the first error I saw--
MSI motherboard boot manager not found.
It requested a system image backup which I did not have. Starting over might cure this but
I'm not much aware of how the system image is made-- something else to do.
Then another restart attempt gave an error screen called:
Windows Boot Manager saying
File \Boot\BCD
I have not done a wider search on this error message yet. But I'm here to ask
Sevenforums: Can this error be fixed by running the Repair disk in cmd mode for the
"Fix boot" routines?
I don't know if I can get to the MSI motherboard disk yet. That would normally run
after the Win7 is installed. Using it within Win7 did not load any of that at all.\\
An error occurred while attempting to read the boot configuration data file
I'm re-reading this thread. The answer is that from my experience anything you do to install takes all your data: XP had a repair routine that worked if you were careful. I had used that
many times. With the clean install you suggest I don't know that the famous 'all data will lost'\warning shows up.
Does anyone know if subsequent versions of Windows has actually made a usable repairr tool similar to XP ( not Win7)?
Just now I am gathering info from Microsoft and Sevenforums to correct the bootmgr
not found and assciated errors.
Last edited by loninappleton; 26 Mar 2017 at 13:48.
Boot manager not found is an error that I'm getting _the second_ time I attached the
sysprepped drive to that same MSI motherboard. What would cause this failure after the OS
had successfully booted (though at a different base resolution)?
If I had thought to run MSI system disk on the first bootup it might have fixed something.
Now I am going to Microsoft to find the hard to understand routines to find where BCD is.
The HD is minimally and siply configured. I don't know if a new thread is needed but I'll
continue here for anyone interested. If I can get through it, it will be a lesson well-kept\for the
future.
Still don't know why this is needed and not encountered and solved earlier.
I took the solved mark off of this.
Very confused. After all went well at first boot up to the new motherboard I removed it
to storage as a test HD. Today I intended to run the MSI motherboard system disk to update the drivers.
The sysprepped disk completely failed to load: a black screen, not even a blue one: dead.
I'm running the Partition Wizard cd to learn of any MBR problems. It's a big disappointment and I don't know a cure for it.
But I'm glad there's an 'unsolved' button on here so people aren't caught in a bind without the new info.
Last edited by loninappleton; 27 Mar 2017 at 12:16.
I'm back.
I retraced my steps and realized I had made some small changes in the MSI BIOS.
I went to BIOS and asked for FailSafe Default settings.
That got this sysprepped disk going as I has seen before.
Will leave this unsolved yet for any other shake-ups.
Last edited by loninappleton; 27 Mar 2017 at 12:17.
Continuing,
I ran the MSI motherboard setup disk yesterday. Next will try a cold boot again.
My last note on this. On that test disk I tried the routine for MBR refresh using Partition magic as described in a tutorial. I repeated some small changes in BIOS.
Leaving the BIOS at Fail Safe Default setting was necessary to get a good boot again.
That should satisfy any remaining questions.
Quote