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

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

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

Show all headers | View raw

On 2025/7/30 2:55:55, Paul wrote:
> 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.

[]

>> 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!>

[]

> 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/


As I've just replied to "Here You Go", I don't think it's a %path^
problem: the two variants currently not working are a scheduled task
that explicit calls it with its location - "C:\TQ\NEW-COOK.BAT" - and
(as shown in the above screenshot - look at what's visible _around_ the
error box) physically going to the folder and double-clicking on it.>
> 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
> 
> *******

I don't understand you there. (My fault, I'm sure.)>
> It's possible there is something peculiar about where or how that folder

I'm pretty sue I made the TQ folder in a fairly conventional way.

> got unpacked, but what tool would we use which is knowledgeable enough,
> to figure out what is wrong ?
> 
>    [Picture]

(Yeuch, tall and thin - looks like it's from a 'phone, or something
trying to imitate one. However ...)>
>     https://i.postimg.cc/X7GPKrtP/Co-Pilot-My-BAT-File-Wont-Start.gif
> 
> The only word that stood out there was "Permissions".
> 
... Well, option 3 - "The .BAT file type might be incorrectly
associated" sounded plausible. I haven't consciously changed anything. I
didn't quite understand what it was saying, but when I typed (in a
command window - what I typed and what came back are shown here between
<>, because some of them include "s) <assoc .bat>, it came back
<.bat=batfile>; when I typed <ftype batfile> it came back
<batfile="^1" %*>, which _seemed_ to match what that image was saying
should be returned.

option 5 "lack of permission to access the file or folder" - well, I can
run it by "Open command window here" and then typing its name (without
the .bat), or from File Explorer I can select Edit and see its contents,
so I don't _think_ there's any permission problem! (I've just tried a
Take Ownership on the folder - no, still says "can't find" if I
double-click on it.) Your image suggests right-clicking the .bat file
and selecting <"Open with" -> "Command Prompt">; if I right-click it,
"Open With" isn't one of the options. (There's "Open" - that just gives
the "can't find" box.)

Ah, I just tried it's last line - Run as Administrator - and (after the
UAC prompt) _something_ happened! Too quickly to see - but I know it
didn't actually work. Quick use of the Print Scrn key lets me see that:
I think the batch file ran, but when it called other files in that
directory, it couldn't find them (fair enough, as run-as-administrator
seems to run from C:\Windows\system32, not where the thing being run
is). Modified batch file so it refers to any file by full path name.
Still "can't find" if double-clicked on, but now does run OK if
right-clicked and run ad admin. Hmm, System Scheduler doesn't have a run
as admin setting for its scheduled tasks. And there doesn't seem to be a
way to change the properties of the batch file itself to do so - which
is reasonable enough.

I'll live with it; I know the way round it, and it'll probably be OK
after next boot anyway.

> *******
> 
> 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
-- 
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

just because you are offended - doesn't mean you are right

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