Access Denied - Install the Everything Service

[ChrisGreaves]

Everything Version 1.5.0.1383a (x64) on a Windows7 DELL laptop.

I know that reboot, and then un/reinstall is an option, but have postponed that until I get feedback on WHY this error might have occurred. No critical project hangs on this issue.

Accessdenied01.jpg (39.92 KiB) Viewed 4601 times

I am searching for files on drive W:, a SUBSTituted drive mapped to a folder on my Veracrypted data partition T: ("subst W: T:\Greaves\Admin\Domains")
My target files are visible to me with

Code: Select all

ext:doc t: \domains\ 

Accessdenied02.jpg (90.65 KiB) Viewed 4601 times

A quick check with Task Manager shows only ONE "Everything"-like process.

Accessdenied03.jpg (54.38 KiB) Viewed 4601 times

Still in Tools, Options I see that "Everything Service" is checked ON.

I do recall seeing files from my SUBSTituted drives over the past month, but I can't swear that I have located them with Everything.

So the drive mapping is working at the Win7 level, but for all I know the Everything Service has been inactive since my most recent installation of Everything.

At this point I nominate myself as a testbed device to investigate/resolve this issue.
No critical project hangs on this issue.

Thanks, Chris

[void]

Opening the W: volume fails with access denied.

It might have something to do with the subst mapping.
It might have something to do with Everything running as admin.

Could you please send debug logs:

• In Everything 1.5, please make sure the Options window is closed.
• From the Tools menu, under the Debug submenu, click Start Debug Logging.
• From the Tools menu, click Options.
• Click the NTFS tab on the left.
• In Everything 1.5,
• From the Tools menu, under the Debug submenu, click Stop Debug Logging.
  ---This will open your %TEMP%\Everything Debug Log.txt
• Could you please send this file to support@voidtools.com

[ChrisGreaves]

It might have something to do with the subst mapping.
It might have something to do with Everything running as admin.

Void, I remember that you urged me to use Folders rather than FAT/NTFS drives some months ago. That did work.
I had removed the folders to trial a way of tying the Everything Folders options to the BATch file that effects the SUBSTitutions. That work is incomplete which is why I don't have folders set.
My current setting of the SUBSTituted drives as Drives is probably me forgetting your advice.

I will go back and set folders and try indexing w:\ that way; it will almost certainly avoid this reported error.
[later] Yes. Folders still works perfectly. I think you can ignore this reported error. Folders should be used on SUBSTituted drives.

Too I remember your advice about running as Administrator. To the best of my knowledge I am not running Everything as Administrator, neither from the shortcut link nor as a user with Administrative privileges.

[*]Click the NTFS tab on the left.

I added a step after this step, to select the W: drive, in case that generated debug text about that drive.

I had to reboot in this interval but I have repeated the error condition before generating the attached logging text

Cheers, Chris

[tuska]

To the best of my knowledge I am not running Everything as Administrator,
neither from the shortcut link nor as a user with Administrative privileges.

Mmh, in my opinion the option box for "Run as administrator" should be completely empty in this case.
See my comparison picture with the information from the forum.
 

Square-checked_Run as a standard user (currently running as an administrator).png (484.48 KiB) Viewed 4540 times

 
Pictures: Square-checked | Tick-checked:

[void]

Thank you for the logs.

Everything is using the wrong volume GUID.

(\\.\w: instead of \\?\Volume{...-...-...-...-...0a})

I am working on a fix..



For now, please add your w: drive as a folder index under Tools -> Options -> Folders.

[ChrisGreaves]

Everything is using the wrong volume GUID. ... I am working on a fix..

Thanks Void; if it's a genuione bug, well and good, but if it looks like you are fixing a bug that affects the only person left on Earth who uses DOS SUBST in an AutoExec,bat file, then please set it at lowest priority.
Back to "Folders", me! (he wrote, with his bandaged foot )
Cheers, Chris

[therube]

SUBST: X: C:\out\recylererer

.ini:
ntfs_volume_paths=C:,E:,K:,X:
ntfs_volume_guids=\\?\Volume{ee1...},\\?\Volume{56b...},\\?\Volume{75e...},\\?\harddiskvolume3
ntfs_volume_roots=,,,out\recylererer

debug:
2024-08-01 15:06:52.782: Config: ntfs_volumes=[{"path":"X:","volume_name":"\\\\?\\harddiskvolume3","root":"out\\recylererer"}]


FWIW (& I guess I'm not understanding/seeing enough).

So, why am I seeing "harddiskvolume3" rather then a "GUID"?
And what caused the \\.\ rather then \\?\ ?

[void]

So, why am I seeing "harddiskvolume3" rather then a "GUID"?
And what caused the \\.\ rather then \\?\ ?

In the future you will see a volume GUID.

For now, Everything uses \\?\harddiskvolumeX for \device\harddiskvolumeX DOS devices.
\\.\harddiskvolume and \\?\harddiskvolume are the same in this case.

Veracrypt uses the DOS device name: \device\VeraCryptVolumeT
Everything doesn't know how to handle this and attempts to use \\.\t:
This is currently failing for Veracrypt volumes.
The next alpha update will use a volume GUID.

[ChrisGreaves]

Veracrypt uses the DOS device name: \device\VeraCryptVolumeT

I have to ask: Is this Everything-bug due specifically to VeraCrypt, or might it apply to:-
(1) Other encryption programs such as TrueCrypt (from which I migrated ten years ago)
(2) Other programs?

I ask because I still have TrueCrypt on my system and will run a quick test if you think that would be useful.
Cheers, Chris

[void]

I have to ask: Is this Everything-bug due specifically to VeraCrypt, or might it apply to:-
(1) Other encryption programs such as TrueCrypt (from which I migrated ten years ago)

Yes, this is an Everything bug.
The issue also affects Truecrypt.

(2) Other programs?

Yes, any non-physical device.

[ChrisGreaves]

The issue also affects Truecrypt.
Yes, any non-physical device.

Thanks Void

[void]

Everything 1.5.0.1384a fixes an issue with indexing Veracrypt volumes.

Please let me know if you have any troubles with this version.

[ChrisGreaves]

Everything 1.5.0.1384a fixes an issue with indexing Veracrypt volumes.

VOID, I continue to be amazed at the mental contortions you must go through to steer a course through the swamps of complexity in Windows OS and associated applications technology.
Back in 73/74 I took a one-year course in circuitry (starting at the Nand/Nor gate levels and working up to a Cyber 72) and that seems like kindergarten stuff compared to GUIDs and Veracrypt device names! :clapping: :clapping: :clapping:
Cheers, Chris