New
#291
Not sure what that error is exactly but I have the same problem with replacing them while Windows 7 is running and thats why I asked if you have a dual boot with another OS, that way you can boot into the other OS and make all the changes from there without having to worry about a file being in use.
- File-In-Use Replace Utility (inuse.exe): InUse is a command-line tool that performs on-the-fly replacement of files that the operating system currently uses. To download this tool, click the following link:http://download.microsoft.com/downlo...n-us/inuse.exe
This may be of some use, haven't tried it yet but it looks like it might do the job, that's if it works with Windows 7.
Sorry that didn't work for me either when I just tried it, I'm trying to search for a solution and the only thing I have come up with so far is this but it's a bit complex.
How to replace files which are in use in Windows
Replacing files which are in use. For non-core files, the simplest solution is often to reboot to Safe Mode and attempt to replace the files. However, some files, such as core-system files, may be in use even in Safe Mode.
Windows offers the ability to replace files on the next boot. This functionality is used by many software installers. To replace a file follow these steps:
- While logged in as an administrator, launch your registry editor. Note: On Windows NT and Windows 2000 systems, you must use REGEDT32 as the registry value is a Multi-String (MULTI_SZ) type, which is not supported in REGEDIT. REGEDIT on Windows XP or 2003 systems does support MULTI_SZ.
- Browse to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
- Open the MULTI_SZ registry value PendingFileRenameOperations. Create it if it does not exist.
- The format of the entry is as follows:
- On the first line enter \??\ followed by the path of the new file which will be used as a replacement. The replacement file should be located on a local hard disk to ensure it will be accessible on reboot! It is best to put it in a different folder on the same drive as the file it is replacing.
- On the second line enter !\??\ followed by the path of the old file which will be replaced.
- Click OK to save the changes.
- Close the registry editor.
Example:
I want to update C:\WINDOWS\SYSTEM32\NTOSKRNL.EXE with a new kernel C:\NEWKERNEL\NTOSKRNL.EXE. I edit PendingFileRenameOperations so it reads as follows:
\??\C:\NEWKERNEL\NTOSKRNL.EXE
!\??\C:\WINDOWS\SYSTEM32\NTOSKRNL.EXE
Entries made in this value will cause the files to be changed the next time the system is rebooted or started and all entries will be automatically removed from PendingFileRenameOperations.
You should, of course, use extreme caution whenever replacing files, particularly system files, as it could easily render your system non-functional.
Microsoft also MV.EXE as part of the [ame="http://www.amazon.com/exec/obidos/redirect?link_code=ur2&tag=techbytes0a-20&camp=1789&creative=9325&path=http%3A%2F%2Fwww.amazon.com%2Fgp%2Fproduct%2F0735622329%2Fqid%3D1133 466124%2Fsr%3D8-2%2Fref%3Dpd_bbs_2%3Fn%3D507846%2526s%3Dbooks%2526v%3Dglance"]Resource Kit[/ame] which will automate this registry change through a command-line utility.
http://www.techbytes.ca/techbyte101.html
Hi Mark,
In addition to your above post the funcionality is provided by the Movefile and pendfiles command line utilities which are part of Sysinternals
PendMoves and MoveFile
OK not sure if this will work but it seemed to when I just tried it, drag the file you want to replace to the desktop and then replace it with the one you downloaded and repeat for each file and let me know when you have done that and we will go from there.