should of emailed me...
I dont always hang on this group..

You know how to rename a file dont you?
Its that simple, you just have to find the old dated one that is the
backup of it. Then rename it after you have moved the other one and put
the backup in its place, so that its named exactly the same as the one
that is messed up. But copy that one to a folder that you make calling
it, old file system file.... Or something that you want to call it, so
if you need it again, you can just revert back to it in case you choose
poorly of which one is the good backup. There may be more than one
backup file of it. Depending on how much the machine has been used...


The path should be, C; Windows / System32 / config /
You will find it in there inside config folder...
The name should be SYSTEM in all capital letters.
The Type should be File
The Size should be about 17 mb, mine is little more than that....


Now, you might have a folder inside that config folder named RegBack.
Look in there also, to find another one of the same type file that says
on it, SYSTEM and check the size of it, and the Date. The Date
modified should be older, the one on the one that fires up the machine
in the config folder, should be the same date as now time, for its
always modified every time you start the machine....

so what you need to do, is make sure both those files are about the same
size. They should be. The one in the RegBack folder, and the one in
the config folder. Then, if they are, change them, but do not swap
them. What I did, was a I made a new folder in the config folder,
labeling it NewBkp... So that it was not the same as RegBack. And then
I took the SYSTEM file, and cut and paste it from the config folder,
into the NewBkp folder. That way, you know where it is. And, this
will keep you from renaming in it or having to rename it as long as you
do all this in its proper order.... This first of course. Then go in
the RegBack folder, and just copy that one into the config folder, and
when it ask you do you want to replace it, say yes.

Then after that, your done. Turn the machine off like you normally do,
and then restart it again.....

On 4/19/2017 3:27 PM, Roger Mills wrote:
On 19/04/2017 21:43, tesla sTinker wrote:


On 4/18/2017 10:34 AM, Roger Mills wrote:
On 18/04/2017 14:37, philo wrote:
On 04/17/2017 07:55 PM, Dave Doe wrote:
In article , ,
Roger Mills says...

I have a Virtual XP setup for running a few legacy programs which
won't
run on W7-64bit. It's on a laptop running W7-PRO 64.

It's been ok for several years, but today it won't start. It puts up
the
usual little window saying "Starting Virtual Machine" and the
progress
marker starts moving to the right and when it's got about one
third of
the way across after about 40 seconds, the window closes - and that's
that. No error messages or anything. At the point when it closes, I
would expect it to say "Starting integration functions" - or
something
like that - but it doesn't.

I've re-booted numerous times to no avail. Malwarebytes doesn't find
anything amiss.

Anyone got any suggestions what to try next?

Go into Windows Update and see if you have KB2830477 installed.

If you have, remove it. And try VPC again.




That update is three years old, I would expect a more recent update to
be the possible problem.

Indeed. But I've uninstalled the other updates which have been installed
since Virtual XP last worked - to no avail!
dont do that..... your system file is likely corrupt. Go change it
manually. Its inside the windows/system folder. There is a backup that
is kept in the same folder with it somewhere, with a funny extension
name. sometimes even more than one of them. Its just a configuration
file that starts up the machine.... Sometimes they get corrupt. And
then, it don't work anymore... its not the update, so you need to leave
that alone...

So how do I go about restoring the system file?