Shortcut not deletable

I'm working on a Win7 machine and was attempting to perform a clean-up.

All fine except for one shortcut than cannot be deleted... "access denied."



Tried booting from a Win7 DVD and from the command prompt got the same
message.

No big deal, I just booted up with a Linux live CD and tried to delete
from Linux (seen as a symbolic link)...again "access denied."

Finally from a root command prompt tried rm -f

It was still not possible to delete, error I got was "directory not empty."


I then tried whatever rm -d and rm -r

but there is no way to delete that link


Though it's not harming anything, why can't Linux or Windows handle it?

I can move it and rename it...


File system is not corrupted as I ran CHKDSK /F

"philo" wrote in message
...
I'm working on a Win7 machine and was attempting to perform a clean-up.

All fine except for one shortcut than cannot be deleted... "access
denied."



Tried booting from a Win7 DVD and from the command prompt got the same
message.

No big deal, I just booted up with a Linux live CD and tried to delete
from Linux (seen as a symbolic link)...again "access denied."

Finally from a root command prompt tried rm -f

It was still not possible to delete, error I got was "directory not
empty."


I then tried whatever rm -d and rm -r

but there is no way to delete that link


Though it's not harming anything, why can't Linux or Windows handle it?

I can move it and rename it...


File system is not corrupted as I ran CHKDSK /F

You can always used MoveOnBoot, a free program that will take care of things
like that.

http://emcosoftware.com/move-on-boot

Ted.....

On 03/10/2016 06:10 PM, Ted wrote:

X...


File system is not corrupted as I ran CHKDSK /F

You can always used MoveOnBoot, a free program that will take care of
things like that.

http://emcosoftware.com/move-on-boot

Ted.....



Thanks for the reply.
I tired MoveOnBoot, it said file was not locked...but it was unable to
delete it.

I decided to just mark it as hidden and forget about it.

I'm sure the utility will get used elsewhere.

"philo" wrote in message
...
On 03/10/2016 06:10 PM, Ted wrote:

X...


File system is not corrupted as I ran CHKDSK /F

You can always used MoveOnBoot, a free program that will take care of
things like that.

http://emcosoftware.com/move-on-boot

Ted.....



Thanks for the reply.
I tired MoveOnBoot, it said file was not locked...but it was unable to
delete it.

I decided to just mark it as hidden and forget about it.

I'm sure the utility will get used elsewhere.


MoveOnBoot used to allow you to right-click the file and select "Delete file
on next boot."
Don't know if that still applies. Maybe an older version. Good luck.
Ted....

On 03/10/2016 06:48 PM, Ted wrote:


"philo" wrote in message
...
On 03/10/2016 06:10 PM, Ted wrote:

X...


File system is not corrupted as I ran CHKDSK /F

You can always used MoveOnBoot, a free program that will take care of
things like that.

http://emcosoftware.com/move-on-boot

Ted.....



Thanks for the reply.
I tired MoveOnBoot, it said file was not locked...but it was unable to
delete it.

I decided to just mark it as hidden and forget about it.

I'm sure the utility will get used elsewhere.


MoveOnBoot used to allow you to right-click the file and select "Delete
file on next boot."
Don't know if that still applies. Maybe an older version. Good luck.
Ted....





If it saw the file as locked, it would do that
but it was not locked.

Must be because it's not actually a file, but a link.

Windows and Linux evidently do not treat a link as a file.

"philo" wrote in message
...
On 03/10/2016 06:48 PM, Ted wrote:


"philo" wrote in message
...
On 03/10/2016 06:10 PM, Ted wrote:

X...


File system is not corrupted as I ran CHKDSK /F

You can always used MoveOnBoot, a free program that will take care of
things like that.

http://emcosoftware.com/move-on-boot

Ted.....



Thanks for the reply.
I tired MoveOnBoot, it said file was not locked...but it was unable to
delete it.

I decided to just mark it as hidden and forget about it.

I'm sure the utility will get used elsewhere.


MoveOnBoot used to allow you to right-click the file and select "Delete
file on next boot."
Don't know if that still applies. Maybe an older version. Good luck.
Ted....





If it saw the file as locked, it would do that
but it was not locked.

Must be because it's not actually a file, but a link.

Windows and Linux evidently do not treat a link as a file.


Try the older version 1.9.5
http://www.softwarepatch.com/software/moveonboot.html

Ted

On 03/10/2016 06:52 PM, Ted wrote:


Try the older version 1.9.5
http://www.softwarepatch.com/software/moveonboot.html

Ted





Won't do any good as it sees it as NOT being locked.

philo wrote:
On 03/10/2016 06:52 PM, Ted wrote:


Try the older version 1.9.5
http://www.softwarepatch.com/software/moveonboot.html

Ted





Won't do any good as it sees it as NOT being locked.

Does the filename of the .lnk, violate any of the
NTFS rules ? Is the path close to being too long ?
Is the last character in the file name a space ?

Perhaps a combination of a Deny permission above
the link, and some sort of Inheritance setting on
the .lnk itself, might account for it.

I ran into something a couple days ago, that TakeOwn
wouldn't fix, and the area in question wasn't supposed
to have any special properties. I gave up. Some day
I'll learn how to read the ICACLS output.

Paul

On 03/10/2016 07:33 PM, Paul wrote:



Won't do any good as it sees it as NOT being locked.

Does the filename of the .lnk, violate any of the
NTFS rules ? Is the path close to being too long ?
Is the last character in the file name a space ?


The problem seems to be that it is not a file.

It's a folder that is a shortcut to "system32"

I can rename it or move it...but I cannot assign it an extension


Perhaps a combination of a Deny permission above
the link, and some sort of Inheritance setting on
the .lnk itself, might account for it.


According to a Windows "unlocker" utility, it is not even locked.


I just changed it to "hidden" and am now going to just forget the whole
thing

I ran into something a couple days ago, that TakeOwn
wouldn't fix, and the area in question wasn't supposed
to have any special properties. I gave up. Some day
I'll learn how to read the ICACLS output.

Paul

On Thursday, March 10, 2016 at 9:48:48 PM UTC-6, philo wrote:
On 03/10/2016 07:33 PM, Paul wrote:



Won't do any good as it sees it as NOT being locked.

Does the filename of the .lnk, violate any of the
NTFS rules ? Is the path close to being too long ?
Is the last character in the file name a space ?


The problem seems to be that it is not a file.

It's a folder that is a shortcut to "system32"

I can rename it or move it...but I cannot assign it an extension


Perhaps a combination of a Deny permission above
the link, and some sort of Inheritance setting on
the .lnk itself, might account for it.


According to a Windows "unlocker" utility, it is not even locked.


I just changed it to "hidden" and am now going to just forget the whole
thing

I ran into something a couple days ago, that TakeOwn
wouldn't fix, and the area in question wasn't supposed
to have any special properties. I gave up. Some day
I'll learn how to read the ICACLS output.

Paul

I found that Linux will not delete it because the directory is not empty.
Emptying directories manually still resulted in the same result.
What worked for me was to put the directory in the trash and than empty the trash.

Aside from that access denied is most likely a permissions issue and should be able to be remedied with elevated privileges.

Is the shortcut a symbolic link to an application?

Try he
http://linoxide.com/linux-how-to/remove-symbolic-link/

-::-The rm command just removes the link. However it will not delete the target directory.-::-
http://askubuntu.com/questions/21789...ry-in-terminal