Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
Windows Vista File Management Issues or questions in relation to Vista's file management. (microsoft.public.windows.vista.file_management) |
|
LinkBack | Thread Tools | Display Modes |
|
|
|||
lnk file association
Long story short, I'm another one of the dozens of people whose shortcuts and
start menu files have turned into unassociated .lnk files. I've looked at several other threads and tried the fix that they point to, namely the .reg fix file. However, whenever I try to merge the file I get an error message that reads: Cannot import C:\lnk_vista.reg: Not all data was successfully written to the registry. Some of the keys are open by the system or other processes. I've tried closing every program in the task manager that will stay closed and it still gives the error message. I've tried moving the file from C:\ to the desktop, tried running regedit and merging the file through that and no luck. Could it have something to do with the fact that I manually assigned an association to the .lnk extension through the Default Programs option? If so then is there any way to dis-associate them so they can be properly re-associated? Or does anyone know any other way to fix this problem? |
|
|||
lnk file association
Daemonfyre,
Have you verified that you have the right to modify these regkeys? You may have to take ownership of the keys your regfile modifies and then grant yourself (or your group such as Admins) full access. Apply the change recusrively (to the key and all subkeys). The keys are probably HKEY_CLASSES_ROOT\.lnk and HKEY_CLASSES_ROOT\lnkfile. Thanks, Ilia "Daemonfyre" wrote in message ... Long story short, I'm another one of the dozens of people whose shortcuts and start menu files have turned into unassociated .lnk files. I've looked at several other threads and tried the fix that they point to, namely the .reg fix file. However, whenever I try to merge the file I get an error message that reads: Cannot import C:\lnk_vista.reg: Not all data was successfully written to the registry. Some of the keys are open by the system or other processes. I've tried closing every program in the task manager that will stay closed and it still gives the error message. I've tried moving the file from C:\ to the desktop, tried running regedit and merging the file through that and no luck. Could it have something to do with the fact that I manually assigned an association to the .lnk extension through the Default Programs option? If so then is there any way to dis-associate them so they can be properly re-associated? Or does anyone know any other way to fix this problem? |
|
|||
lnk file association
Yes, I went in and verified each item under the key individually, all were
set to admin group(which is me, as this is my home comp and I'm the only user) except one that was set to "TrustedInstaller" I set all of them specifically to my profile, rebooted and tried again, no luck, still gives the error message. "Ilia Sacson [MS]" wrote: Daemonfyre, Have you verified that you have the right to modify these regkeys? You may have to take ownership of the keys your regfile modifies and then grant yourself (or your group such as Admins) full access. Apply the change recusrively (to the key and all subkeys). The keys are probably HKEY_CLASSES_ROOT\.lnk and HKEY_CLASSES_ROOT\lnkfile. Thanks, Ilia "Daemonfyre" wrote in message ... Long story short, I'm another one of the dozens of people whose shortcuts and start menu files have turned into unassociated .lnk files. I've looked at several other threads and tried the fix that they point to, namely the .reg fix file. However, whenever I try to merge the file I get an error message that reads: Cannot import C:\lnk_vista.reg: Not all data was successfully written to the registry. Some of the keys are open by the system or other processes. I've tried closing every program in the task manager that will stay closed and it still gives the error message. I've tried moving the file from C:\ to the desktop, tried running regedit and merging the file through that and no luck. Could it have something to do with the fact that I manually assigned an association to the .lnk extension through the Default Programs option? If so then is there any way to dis-associate them so they can be properly re-associated? Or does anyone know any other way to fix this problem? |
|
|||
lnk file association
Have you tried to do it in safe mode? Do you have any spyware
protectors/registry watchers running? Ilia "Daemonfyre" wrote in message ... Yes, I went in and verified each item under the key individually, all were set to admin group(which is me, as this is my home comp and I'm the only user) except one that was set to "TrustedInstaller" I set all of them specifically to my profile, rebooted and tried again, no luck, still gives the error message. "Ilia Sacson [MS]" wrote: Daemonfyre, Have you verified that you have the right to modify these regkeys? You may have to take ownership of the keys your regfile modifies and then grant yourself (or your group such as Admins) full access. Apply the change recusrively (to the key and all subkeys). The keys are probably HKEY_CLASSES_ROOT\.lnk and HKEY_CLASSES_ROOT\lnkfile. Thanks, Ilia "Daemonfyre" wrote in message ... Long story short, I'm another one of the dozens of people whose shortcuts and start menu files have turned into unassociated .lnk files. I've looked at several other threads and tried the fix that they point to, namely the .reg fix file. However, whenever I try to merge the file I get an error message that reads: Cannot import C:\lnk_vista.reg: Not all data was successfully written to the registry. Some of the keys are open by the system or other processes. I've tried closing every program in the task manager that will stay closed and it still gives the error message. I've tried moving the file from C:\ to the desktop, tried running regedit and merging the file through that and no luck. Could it have something to do with the fact that I manually assigned an association to the .lnk extension through the Default Programs option? If so then is there any way to dis-associate them so they can be properly re-associated? Or does anyone know any other way to fix this problem? |
|
|||
lnk file association
Tried in safe mode, no luck. Also tried in safe mode with command prompt,
still no change. And I've gone through every program that's listed in the task manager that would close and stay closed and tried it again, still no luck. It just keeps giving me that error message. "Ilia Sacson [MS]" wrote: Have you tried to do it in safe mode? Do you have any spyware protectors/registry watchers running? Ilia "Daemonfyre" wrote in message ... Yes, I went in and verified each item under the key individually, all were set to admin group(which is me, as this is my home comp and I'm the only user) except one that was set to "TrustedInstaller" I set all of them specifically to my profile, rebooted and tried again, no luck, still gives the error message. "Ilia Sacson [MS]" wrote: Daemonfyre, Have you verified that you have the right to modify these regkeys? You may have to take ownership of the keys your regfile modifies and then grant yourself (or your group such as Admins) full access. Apply the change recusrively (to the key and all subkeys). The keys are probably HKEY_CLASSES_ROOT\.lnk and HKEY_CLASSES_ROOT\lnkfile. Thanks, Ilia "Daemonfyre" wrote in message ... Long story short, I'm another one of the dozens of people whose shortcuts and start menu files have turned into unassociated .lnk files. I've looked at several other threads and tried the fix that they point to, namely the .reg fix file. However, whenever I try to merge the file I get an error message that reads: Cannot import C:\lnk_vista.reg: Not all data was successfully written to the registry. Some of the keys are open by the system or other processes. I've tried closing every program in the task manager that will stay closed and it still gives the error message. I've tried moving the file from C:\ to the desktop, tried running regedit and merging the file through that and no luck. Could it have something to do with the fact that I manually assigned an association to the .lnk extension through the Default Programs option? If so then is there any way to dis-associate them so they can be properly re-associated? Or does anyone know any other way to fix this problem? |
|
|||
lnk file association
Hmm. Well, let's do it the hard way then. Please install Process Monitor
from he http://www.microsoft.com/technet/sys...ssmonitor.mspx. This nice program allows monitoring all file, registry and other activity. Start it up. Then configure it to show registry activity only (the toolbar button that looks like regedit.exe's icon pressed, other two not pressed), and open the reg file. The message should ask you if you really mean to add that stuff to the registry. Do not press anything, go back to Process Monitor, scroll down to where regedit.exe first appears in the Process Name column. Right-click, Include..., Process Name. Now you only see what's regedit doing to the registry. Clear the view by pressing Control+X keys or the little page and erazer button on the toolbar. Now go back to that confirmation dialog and press Yes. Process Monitor should show all the registry operations that regedit tried to do to change the registry according to the reg file. In the Results column, search for anything other than SUCCESS or NAME NOT FOUND or REPARSE or BUFFER OVERFLOW, these are expected. ACCESS DENIED would be good, or something like that. In the Path column, it should mention where exactly the access is denied. Then try setting right permissions on these keys. Ilia "Daemonfyre" wrote in message ... Tried in safe mode, no luck. Also tried in safe mode with command prompt, still no change. And I've gone through every program that's listed in the task manager that would close and stay closed and tried it again, still no luck. It just keeps giving me that error message. "Ilia Sacson [MS]" wrote: Have you tried to do it in safe mode? Do you have any spyware protectors/registry watchers running? Ilia "Daemonfyre" wrote in message ... Yes, I went in and verified each item under the key individually, all were set to admin group(which is me, as this is my home comp and I'm the only user) except one that was set to "TrustedInstaller" I set all of them specifically to my profile, rebooted and tried again, no luck, still gives the error message. "Ilia Sacson [MS]" wrote: Daemonfyre, Have you verified that you have the right to modify these regkeys? You may have to take ownership of the keys your regfile modifies and then grant yourself (or your group such as Admins) full access. Apply the change recusrively (to the key and all subkeys). The keys are probably HKEY_CLASSES_ROOT\.lnk and HKEY_CLASSES_ROOT\lnkfile. Thanks, Ilia "Daemonfyre" wrote in message ... Long story short, I'm another one of the dozens of people whose shortcuts and start menu files have turned into unassociated .lnk files. I've looked at several other threads and tried the fix that they point to, namely the .reg fix file. However, whenever I try to merge the file I get an error message that reads: Cannot import C:\lnk_vista.reg: Not all data was successfully written to the registry. Some of the keys are open by the system or other processes. I've tried closing every program in the task manager that will stay closed and it still gives the error message. I've tried moving the file from C:\ to the desktop, tried running regedit and merging the file through that and no luck. Could it have something to do with the fact that I manually assigned an association to the .lnk extension through the Default Programs option? If so then is there any way to dis-associate them so they can be properly re-associated? Or does anyone know any other way to fix this problem? |