Hi All,

First time poster here.

I have just backed up my system drive by creating an ISO image. I have
then restored the Image onto a WD Raptor Hard Drive (runs at 10000rpm
I'll have you know!). Now, the first startup worked fine, no problems.
Loaded into the Vista desktop and was able to do what I wanted.

However, subsequent startups have allowed me to log in, but have then
had the message on the screen "Preparing Desktop", only the desktop to
turn out to be nice and blue, with nothing on it, apart from the mouse
pointer. I am able to access the Task Manager from here though, and on
further inspection it appears that in the processes list "explorer.exe"
is not running. I have tried to carry out a installation repair using
the Windows Vista Home Premium x64 DVD, but this came back stating that
there are no problems and Vista previously started up with no problems.
I have now plugged my slightly older and clunkier hard drive back in to
try and look for answers..............

.......Can any of you kind people let me know how to force Vista to run
"explorer.exe"? Or at least point me in the right direction.

Much obliged,

Roger Morrison


--
Roger Morrison

Roger Morrison schreef in bericht
...

Hi All,

First time poster here.

I have just backed up my system drive by creating an ISO image. I have
then restored the Image onto a WD Raptor Hard Drive (runs at 10000rpm
I'll have you know!). Now, the first startup worked fine, no problems.
Loaded into the Vista desktop and was able to do what I wanted.

However, subsequent startups have allowed me to log in, but have then
had the message on the screen "Preparing Desktop", only the desktop to
turn out to be nice and blue, with nothing on it, apart from the mouse
pointer. I am able to access the Task Manager from here though, and on
further inspection it appears that in the processes list "explorer.exe"
is not running. I have tried to carry out a installation repair using
the Windows Vista Home Premium x64 DVD, but this came back stating that
there are no problems and Vista previously started up with no problems.
I have now plugged my slightly older and clunkier hard drive back in to
try and look for answers..............

......Can any of you kind people let me know how to force Vista to run
"explorer.exe"? Or at least point me in the right direction.

You have to clone the original to the new drive, and change the drives.

--

Wie alles begrijpt, die alles vergeeft...
____________________
NIGH****CHER
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

I've solved this problem now. Basically what happened was when I
restored the backup image to the new hard drive I allowed the software
to automatically nominate a drive letter (turned out be e, which meant
that windows would startup as long as the older drive was connected and
switched on, as windows was still taking the majority of its system
resources from the c: drive, which is we know, if windows are looking
for resources that arent there, it wont function properly!!

So basically, I booted back into the older drive, formatted the new
drive and restored the image back to the new drive, telling the software
not to allocate a drive letter.

Then 1 hour later and 2 intances of installation repair, the new drive
is now working!

I hope this helps anyone else like me, who decided to make a pigs ear
out of a simple task!!


--
Roger Morrison

If you ever run across this again, have a look at this article (it applies to
Vista as well).
http://support.microsoft.com/kb/223188
--
Paul


"Roger Morrison" wrote:


I've solved this problem now. Basically what happened was when I
restored the backup image to the new hard drive I allowed the software
to automatically nominate a drive letter (turned out be e, which meant
that windows would startup as long as the older drive was connected and
switched on, as windows was still taking the majority of its system
resources from the c: drive, which is we know, if windows are looking
for resources that arent there, it wont function properly!!

So basically, I booted back into the older drive, formatted the new
drive and restored the image back to the new drive, telling the software
not to allocate a drive letter.

Then 1 hour later and 2 intances of installation repair, the new drive
is now working!

I hope this helps anyone else like me, who decided to make a pigs ear
out of a simple task!!


--
Roger Morrison