Missing or Not Valid File in Win XP Mode- is it repairable?

[racewizard]

Hello, this is my first post. Generally do not run into problems, but this is a whopper for me for autoCAD 2006LT architect runs on xp only which is the primary reason am running xp still, and doing it on the virtual machine.

I am suddenly getting a pop-up "Cannot start Windows XP Mode"........One or more files are either missing of not valid.

Is there a way to replace/repair, etc, the files so that XP Mode will start again without having to create a new Windows XP environment?

The reason I so hope this is possible is that my version of autoCAD is no longer supported. Same as XP is no longer supported. Autodesk only supports programs 2010 and later, even though when I paid for that program it was specifically based on a "permanent" license, but HaHa. If I re-install autoCAD have to obtain a code from Autodesk to validate and get off the "temporary use" time limit. They do not want to mess with it.

When I go to "All Programs" and down to Windows Virtual PC, and click that a sub-menu drops that has two items: Windows Virtual PC and Windows XP Mode.......clicking on Windows Virtual PC...brings up a screen that says "This folder is empty" though have no idea how this could be. Clicking on Windows XP Mode brings up the pop-up as noted above "Cannot start...."

However, right clicking on Windows XP Mode and clicking Properties brings up the Properties...clicking "Security" brings up Group of user names for permissions.....all the noted have some greyed out or black checks in the "Allow" column, nothing is checked for any on "Deny"...so apparently this installation is still on the hard drive, it simply will not start or boot up.

There are no "Previous Versions" that I can restore to, unfortunately.....

Any help is certainly appreciated!

 

[iko22]

Hello racewizard, welcome to Seven Forums.

Presumably you are talking about SFC /scannow results. There is a way to replace damaged files, but first, run DISM /online /cleanup-image from an elevated command prompt window. That can repair damaged files that SFC cannot. DISM only works in Windows Vista and after, it might repair your computer's files associated with cannot start XP mode problem.

 

[racewizard]

Yes sir...had previously run SFC /scannow which found no integrity errors (as it noted)....already had tried the DISM command and receive:

Error 87

An error occurred while processing this command.
Ensure that the command-line arguments are valid.

(command-line as typed is: DISM /online /cleanup-image)

right now am running SFC /scannow again and will run it three times to see if it helps anything....would be nice if could figure out that DISM run, clear up that Error 87, and get it to work....looked at the forum posts on Error 87, but no avail

Just finished the first SFC /scannow

Windows Resource Protection did not find any integrity violations.

Restarting to do another scan

 

[racewizard]

OK tried everything today....ran the SFC /scannow 3 times, nothing.....ran CHKDSK..took hours...nothing.....
DISM...error 87

Thanks Very Much!

 

[iko22]

If CHKDSK took hours, then either the disk drive being scanned is very large or there is a fault with it. What is the make and capacity of the drive?

DISM error 87 could mean that the command was not executed from an elevated command prompt. If that was the case then try executing the command again, from the elevated cmd prompt window.

 

[racewizard]

4 GB Intel(R) Core(TM)2 Duo CPU T8100 2.10 2.10

I was running the command in the command prompt window on c:\Windows\system32

 

[iko22]

4 GB Intel(R) Core(TM)2 Duo CPU T8100 2.10 2.10

I was running the command in the command prompt window on c:\Windows\system32

1) I was asking for the make/capacity of the Hard Disk Drive. You give me your CPU specs.

2) A command prompt window is not the same as an elevated command prompt. An elevated command prompt is also known as an administrators command prompt. To start this type of window, type cmd into the rb: search box, and click it with a right-mouse click, then select Run As Administrator, from the drop-down list.

Sorry for the confusion.