Recovery Console - 'File Could Not Be Copied' Error

[Guest]

Help...my kids appear to have trashed the registry while installing a new
game on their PC, now it's a vegetable and won't boot. Anyway I'm following
one of the Microsoft technotes and attempting to backup existing registry
files, then delete the registry files from existing location, then copy from
repair folder. When I attempt the first step of copying existing registry
files I receive "The file could not be copied". I've attempted this several
times...I'm sure I have the correct paths. I've also used SET command to
allowallpaths. And Yes...I know that poking around the registry is a
dangerous thing.

 

[Maurice N ~ MVP]

Which file failed the copy? and did you make sure it is present in the source folder?

I assume you are following the MS KB article of recovery of registry.

what step are you at & is the failure while in recovery console, or while back in Windows ?

 

[David Candy]

You have to edit the registry to allow set to work?
--
--------------------------------------------------------------------------------------------------
Goodbye Web Diary
http://margokingston.typepad.com/harry_version_2/2005/12/thank_you_and_g.html#comments
=================================================
Which file failed the copy? and did you make sure it is present in the source folder?

I assume you are following the MS KB article of recovery of registry.

what step are you at & is the failure while in recovery console, or while back in Windows ?

 

[Guest]

Any of the files I try to copy. Yes, the file is present in the source and
the temporary directory exists... Here's an example..
copy c:\windows\system32\config\software c:\windows\tmp\software.bak

 

[Guest]

Joefish,

What is the exact error message (as displayed on the screen) you receive
when you first startup the computer ?

Jason

 

[Maurice N ~ MVP]

Joe,
Did the creation of the temporary folder work, and created in the correct location? ( the step at MD )
make sure c:\windows\tmp exists

assuming you have a copy of kb 307545 at hand

 

[ANONYMOUS]

If boot-up is the problem then try this:

1) Get a blank formatted floppy disk
2. Copy the Ntdetect.com and NTLDR files from the I386 folder on the XP
CD-ROM to this floppy disk (or from a XP system that is working from c:\
- unhide all hidden files first and enable file extensions to be
visible).
3. Rename the NTLDR file to Setupldr.bin if copied from CD-ROM.
4. Create a Boot.ini file in Notepad by copying the following:


[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /noexecute=optin /fastdetect

This disk will allow you to bootup the HD. You can then do the backups
of
your data before trouble shooting.

 

[Maurice N ~ MVP]

Joe's system has a corrupted registry. This will not help to get around his currentissue. It would fail due to registry problem.

Nevertheless, everyone should have this bootup diskette stored somewhere.

--
Maurice N
MVP Windows - Shell / User
-----

If boot-up is the problem then try this:

1) Get a blank formatted floppy disk
2. Copy the Ntdetect.com and NTLDR files from the I386 folder on the
XP CD-ROM to this floppy disk (or from a XP system that is working
from c:\
- unhide all hidden files first and enable file extensions to be
visible).
3. Rename the NTLDR file to Setupldr.bin if copied from CD-ROM.
4. Create a Boot.ini file in Notepad by copying the following:


[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /noexecute=optin /fastdetect

This disk will allow you to bootup the HD. You can then do the
backups of
your data before trouble shooting.

Help...my kids appear to have trashed the registry while installing
a new game on their PC, now it's a vegetable and won't boot. Anyway
I'm following one of the Microsoft technotes and attempting to
backup existing registry files, then delete the registry files from
existing location, then copy from repair folder. When I attempt the
first step of copying existing registry files I receive "The file
could not be copied". I've attempted this several times...I'm sure I
have the correct paths. I've also used SET command to allowallpaths.
And Yes...I know that poking around the registry is a dangerous
thing. --
JoeFish

 

[Guest]

Maurice,
Yes, the MD created the directory... and yes I'm working from KB 307545.

 

[Guest]

Message at boot indicates problem with file ... Windows\System32\Config\System

If I try to use a utility disk to access the system (boot disk) it indicates
problem with file... Windows\System32\Config\Software and also that Registry
Hive is Corrupted.

The combination of these two led me to KB 307545

 

[Maurice N ~ MVP]

very good !
while in Recovery Console, do the following set commands (even though, I believe you did 1 already)

set AllowAllPaths = TRUE

set AllowWildCards = TRUE

set NoCopyPrompt = TRUE

Joe, make sure you are not missing the space (when typing copy command) between source file-location & the destination

 

[Maurice N ~ MVP]

Joe: Is your Windows directory at \Windows or \WINNT ?? That may be your issue with the copy command.

If you have \WINNT, substitute that in lieu of \Windows ( as used in kb article).

 

[Guest]

Does the Error message say "......config\software is MISSING or corrupt"?
You can't copy a missing file, hence the "file could not be copied" message.
Same, if you renamed it; the file "as named" may not exist.

 

[Guest]

In the Windows\System32\Config directory the file exists... all I'm trying to
do is copy it to a temp directory before deleting it from the source directory

 

[Guest]

Maurice,
I had previously did the set commands and my directory is indeed Windows

 

[Maurice N ~ MVP]

Joe,

Make a note of what directory you're at now.
I suggest you change directory to source folder. Type in

cd \windows\system32\config

when successful, you should be able to do a DIR. Then proceed with copy

 

[Guest]

You can rename it at the source as well. Not 100% necessary to copy it to the
tmp folder.

Boot into recovery console and ensure your at the c:\windows prompt.
Type in cd system32\config enter
ren system system.bak
ren software software.bak
ren security security.bak
ren sam sam.bak
ren default default.bak
copy c:\windows\repair\system enter
copy c:\windows\repair\software enter
copy c:\windows\repair\security enter
copy c:\windows\repair\sam enter
copy c:\windows\repair\default enter

Type exit to see if you can boot. You will now have to perform the next
steps of the article to complete.

 

[Guest]

Gee, now why didn't I think of just renaming the files in the current
directory? I guess I'm too close to the problem...or maybe it's those nine
years of Catholic schools and only working from the script. Anyway, that
worked...I was able to get into SAFE Mode on subsequent...that launched me
into a whole new set of problems... Time to start new thread...

 

[ANONYMOUS]

Gee, now why didn't I think of just renaming the files in the current
directory? I guess I'm too close to the problem...or maybe it's those nine
years of Catholic schools and only working from the script. Anyway, that
worked...I was able to get into SAFE Mode on subsequent...that launched me
into a whole new set of problems... Time to start new thread...

Would it not be easier to do a clean install of OS and start from
scratch? The system must have become very unstable and the problems
will inevitably return.