PendingFileRenameOperations

  • Thread starter Thread starter John A Grandy
  • Start date Start date
J

John A Grandy

this key is causing problems:

HKLM\System\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations

is it ok to delete the key?

if not, how should i modify it to erase its current information? when i
right-click and select modify i get a binary editor. should i just wipe all
hex chars shown?
 
John A Grandy said:
this key is causing problems:

is it ok to delete the key?
Click to expand...

Yes, it's okay to delete PendingFileRenameOperations (which is a value
name, not a key).
if not, how should i modify it to erase its current information? when i
right-click and select modify i get a binary editor. should i just wipe all
hex chars shown?
Click to expand...

If the data is not readable as characters, that's probably the cause of
your problem. Deleting the value name should clear it up.
 
John A Grandy said:
this key is causing problems:

is it ok to delete the key?
Click to expand...

Yes, it's okay to delete PendingFileRenameOperations (which is a value
name, not a key).
if not, how should i modify it to erase its current information? when i
right-click and select modify i get a binary editor. should i just wipe all
hex chars shown?
Click to expand...

If the data is not readable as characters, that's probably the cause of
your problem. Deleting the value name should clear it up.
 
John said:
this key is causing problems:

HKLM\System\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations

is it ok to delete the key?
Click to expand...

*Only* if it still is present after a reboot, it should remove itself at
computer startup, after the file rename operations are done.

(and note, it is a registry value and not a key).

if not, how should i modify it to erase its current information? when i
right-click and select modify i get a binary editor. should i just wipe all
hex chars shown?
Click to expand...

If you use regedt32.exe instead of regedit.exe to view the data in this value,
it is presented in a more human readable way.
 
John said:
this key is causing problems:

HKLM\System\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations

is it ok to delete the key?
Click to expand...

*Only* if it still is present after a reboot, it should remove itself at
computer startup, after the file rename operations are done.

(and note, it is a registry value and not a key).

if not, how should i modify it to erase its current information? when i
right-click and select modify i get a binary editor. should i just wipe all
hex chars shown?
Click to expand...

If you use regedt32.exe instead of regedit.exe to view the data in this value,
it is presented in a more human readable way.
 
"John A Grandy" said in news:%[email protected]:
this key is causing problems:

HKLM\System\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations

is it ok to delete the key?

if not, how should i modify it to erase its current information?
when i right-click and select modify i get a binary editor. should i
just wipe all hex chars shown?
Click to expand...

This registry key is used when installing software and it has to replace
existing files by the same filenames. Since the files may be currently
inuse, the install cannot delete them. So it adds the directives in this
registry key, tells you a reboot is required, and on startup Windows will
perform the rename or delete directives before loading the program(s).

Error Message: The Installation/Removal of a Previous Program Was Not
Completed
http://support.microsoft.com/?kbid=310335

How to Replace In-Use Files at Windows Restart
http://support.microsoft.com/?kbid=181345

Error Message: A Previous Installation Has Pending Work Requiring a Reboot
http://support.microsoft.com/?kbid=312444

In fact, Microsoft has an "inuse" program you can get to let you do the same
thing. If there is a file that you want to replace but it is currently
inuse, use their "inuse.exe" utility to move a replacement file atop an old
one (after the reboot).

How to Replace Currently Locked Files with Inuse.exe
http://support.microsoft.com/?kbid=228930

Free Windows 2000 Resource Kit Tools for Administrative Tasks
http://support.microsoft.com/?kbid=274305
 
"John A Grandy" said in news:%[email protected]:
this key is causing problems:

HKLM\System\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations

is it ok to delete the key?

if not, how should i modify it to erase its current information?
when i right-click and select modify i get a binary editor. should i
just wipe all hex chars shown?
Click to expand...

This registry key is used when installing software and it has to replace
existing files by the same filenames. Since the files may be currently
inuse, the install cannot delete them. So it adds the directives in this
registry key, tells you a reboot is required, and on startup Windows will
perform the rename or delete directives before loading the program(s).

Error Message: The Installation/Removal of a Previous Program Was Not
Completed
http://support.microsoft.com/?kbid=310335

How to Replace In-Use Files at Windows Restart
http://support.microsoft.com/?kbid=181345

Error Message: A Previous Installation Has Pending Work Requiring a Reboot
http://support.microsoft.com/?kbid=312444

In fact, Microsoft has an "inuse" program you can get to let you do the same
thing. If there is a file that you want to replace but it is currently
inuse, use their "inuse.exe" utility to move a replacement file atop an old
one (after the reboot).

How to Replace Currently Locked Files with Inuse.exe
http://support.microsoft.com/?kbid=228930

Free Windows 2000 Resource Kit Tools for Administrative Tasks
http://support.microsoft.com/?kbid=274305
 
Back
Top