Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.comp.os.windows-10 > #182807 > unrolled thread

Why can't I delete

Started byFrankie <frankie@nospam.usa>
First post2025-03-07 06:25 +0000
Last post2025-03-11 06:03 +0000
Articles 4 — 2 participants

Back to article view | Back to alt.comp.os.windows-10


Contents

  Why can't I delete Frankie <frankie@nospam.usa> - 2025-03-07 06:25 +0000
    Re: Why can't I delete Frankie <frankie@nospam.usa> - 2025-03-07 16:50 +0000
      Re: Why can't I delete Stan Brown <the_stan_brown@fastmail.fm> - 2025-03-08 09:25 -0800
        Re: Why can't I delete Frankie <frankie@nospam.usa> - 2025-03-11 06:03 +0000

#182807 — Why can't I delete

FromFrankie <frankie@nospam.usa>
Date2025-03-07 06:25 +0000
SubjectWhy can't I delete
Message-ID<vqe3he$fq7$1@neodome.net>
I switch to admin and I still can't delete.
 "Could not find this item"
 "This is no longer located in C:\inetpub."
 "Verify the item's location and try again."

It has nothing to do with rebooting as they've been there over many boots.

It has nothing to do with inetpub because I can create a folder and move
that folder around which contains the items that I can't delete. I can put
it anywhere and it still has the exact same error message (other than the
path of course changes depending on where I put the top-level folder).

I've already descended down to the bottom and deleted anything that would
delete and moved up and deleted and moved up, but this still won't die.

I switch to an admin prompt but it still won't delete.
There's a space at the end of some of the directories.

So the error as admin on the command line is different:
 "The system cannot find the path specified."

What's a super powerful just-delete-the-damn-thing command I can run?

[toc] | [next] | [standalone]


#182811

FromFrankie <frankie@nospam.usa>
Date2025-03-07 16:50 +0000
Message-ID<vqf84s$25i7$1@neodome.net>
In reply to#182807
On 7/3/2025, Frankie wrote:

> What's a super powerful just-delete-the-damn-thing command I can run?

I think I figured it out. The "x" command did it. dir /x

That gave me the hidden 8+3 tilde name.
I could delete the 8+3 name (but not a long name with a space at the end).

[toc] | [prev] | [next] | [standalone]


#182823

FromStan Brown <the_stan_brown@fastmail.fm>
Date2025-03-08 09:25 -0800
Message-ID<MPG.42361d6ca08ff8749903bf@news.individual.net>
In reply to#182811
On Fri, 7 Mar 2025 16:50:39 -0000 (UTC), Frankie wrote:
> I could delete the 8+3 name (but not a long name with a space at the end).
> 

Not even in quotes?  

del "blahblahblah.xys " ?

That worked for me.


-- 
Stan Brown, Tehachapi, California, USA         https://BrownMath.com/
Shikata ga nai...

[toc] | [prev] | [next] | [standalone]


#182855

FromFrankie <frankie@nospam.usa>
Date2025-03-11 06:03 +0000
Message-ID<vqojmv$1deo$1@neodome.net>
In reply to#182823
On 8/3/2025, Stan Brown wrote:

>> I could delete the 8+3 name (but not a long name with a space at the end).
>> 
> 
> Not even in quotes?  
> 
> del "blahblahblah.xys " ?
> 
> That worked for me.

I tried everything (except the "DIR /X" trick) for weeks.
Including the doublequotes, which was an early method.

For months, the only thing I could do was move every legitimate filespec
that was inside the poisoned folder, until only the bad filespec remained.

And then I moved the poisoned filespec's top-level folder to a "junk"
location. Every week (or so), a script I wrote that creates files would
falter, and then I'd get another poisoned folder. Which I'd move to "junk".

Over time, they added up, until I got so frustrated, I asked for help here.
But in the interim, I kept looking for solutions, and found it with "X".

DIR /X
DEL 8+3

It's interesting that, in some ways, 8+3 is still very much inside Windows.

[toc] | [prev] | [standalone]


Back to top | Article view | alt.comp.os.windows-10


csiph-web