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

Groups > alt.comp.os.windows-10 > #186361

Re: Windows cannot see a file that's definitely there?!?

Show all headers | View raw

On Tue, 7/29/2025 6:41 PM, J. P. Gilliver wrote:
> On 2025/7/29 21:27:33, Carlos E.R. wrote:
>> On 2025-07-29 22:10, J. P. Gilliver wrote:
>>> See https://255soft.uk/temp/Clipboard_07-29-2025_01.gif - which was
>>> taken immediately after double-clicking the file. As you can see, it's
>>> definitely there.
>>>
>>> If I right-click it and select edit, it opens in Notepad (it's just a
>>> batch file, only five lines, two of which are rem and one blank). What's
>>> more, I just tried "Open command window here" and typed the filename
>>> (without the .bat of course) and it ran fine. (Then double-clicked it
>>> from Explorer again, in case it had "got better" - it hadn't.)
>>
>> Type "NEW" then tab. maybe there is an extra space or hidden char.
>>
> No, this has been working fine for yonks - just W10 sometimes decides it
> can't see what's under its nose. (Typing its name in a command window -
> without any extra characters - made it run, too.) It should have run
> just now, but obviously didn't. I'll go to that directory and open a
> command prompt now - yes, it ran fine, so the _system_ _can_ access it!>
>>>
>>> This has happened before (in Windows 10 - I don't remember it ever under
>>> 7 or before); I don't know what triggers it. This only happens
>>> sometimes; normally, the batch file (which I have as a scheduled task
>>> [using System Scheduler] to run 42 minutes past each hour) runs fine,
>>> either at its appointed time or if I run it manually.
>>
>> -- 
> J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf
> This was before we knew that a laboratory rat, if experimented upon, will
> develop cancer.		 	[Quoted by] Anne (annezo@aol.com), 1997-1-29
> 

You can see in the article here, there is more to Windows than just a %path%.
This article is dated 2010, and Metro.Apps might not be included here.

https://helgeklein.com/blog/how-the-app-paths-registry-key-makes-windows-both-faster-and-safer/

And while there is this mechanism (with more than one kind of "thing" in it),
this isn't a solution to "where is my stuff" either. This is not an exhaustive
mechanism. Neither apparently, is a WMIC script.

   explorer.exe shell:appsFolder

*******

It's possible there is something peculiar about where or how that folder
got unpacked, but what tool would we use which is knowledgeable enough,
to figure out what is wrong ?

   [Picture]

    https://i.postimg.cc/X7GPKrtP/Co-Pilot-My-BAT-File-Wont-Start.gif

The only word that stood out there was "Permissions".

*******

SuperFetch/Sysmain is a way for your executables-activities to be noted
and for the item to be pre-loaded into memory. But this is not going to
prevent a path resolution issue from stopping launch. Sysmain makes
the item potentially launch faster, because it operates a cache for you,
but it should not influence whether a security feature applies or
a security feature is bypassed. It's not intended for "hacking" the system.

https://en.wikipedia.org/wiki/Windows_Vista_I/O_technologies#SuperFetch

   Paul

Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-29 21:10 +0100
  Re: Windows cannot see a file that's definitely there?!? "Carlos E.R." <robin_listas@es.invalid> - 2025-07-29 22:27 +0200
    Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-29 23:41 +0100
      Re: Windows cannot see a file that's definitely there?!? Here You Go <invalid@invalid.invalid> - 2025-07-29 22:55 +0000
        Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-30 13:58 +0100
          Re: Windows cannot see a file that's definitely there?!? MikeS <MikeS@fred.com> - 2025-07-30 18:12 +0100
            Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-30 22:32 +0100
              Re: Windows cannot see a file that's definitely there?!? Here You Go <invalid@invalid.invalid> - 2025-07-30 22:08 +0000
                Re: Windows cannot see a file that's definitely there?!? Here You Go <invalid@invalid.invalid> - 2025-07-30 22:57 +0000
                Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-31 01:00 +0100
      Re: Windows cannot see a file that's definitely there?!? Paul <nospam@needed.invalid> - 2025-07-29 21:55 -0400
        Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-30 18:59 +0100
      Re: Windows cannot see a file that's definitely there?!? Herbert Kleebauer <klee@unibwm.de> - 2025-07-30 07:18 +0200
  Re: Windows cannot see a file that's definitely there?!? VanguardLH <V@nguard.LH> - 2025-07-29 21:53 -0500
    Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-30 21:06 +0100
      Re: Windows cannot see a file that's definitely there?!? VanguardLH <V@nguard.LH> - 2025-07-30 15:45 -0500
        Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-30 23:07 +0100
          Re: Windows cannot see a file that's definitely there?!? VanguardLH <V@nguard.LH> - 2025-07-31 01:13 -0500
            Re: Windows cannot see a file that's definitely there?!? "J. P. Gilliver" <G6JPG@255soft.uk> - 2025-07-31 16:01 +0100

csiph-web