Everything runs, Finds NTFS Drives at Medium Integrity

[therube]

Everything (no service) runs, & does Find NTFS Drives, at a Medium Integrity level, Win7 x64, Admin account, but not having stated Everything "As Administrator" ?

Thought that was not supposed to happen?

Startup, while not slow, is quite a bit slower starting that way, then when Run As Adminstrator.
Same number of files found in each case.

[therube]

Something strange going on ...

With (& it was 644b), this did happen.

Putting in 645b & attempting the same, all I got was 3 objects; C: E: & M:, nothing more.

Code: Select all

WM_ACTIVATE 00000000 00000000, lastfocus 0054065e, current focus 0054065e
WM_ACTIVATE 00000001 00000000, lastfocus 0054065e, current focus 00000000
search 'a' filter ''
term 0072ce08, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: a
create thread PeakWorkingSetSize: 9494528, WorkingSetSize: 9486336
found 0 folders, size 0, db search time taken: 0.000013 seconds
found 0 files, size 0, db search time taken: 0.000008 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000196 seconds
search 'ab' filter ''
term 0072ce58, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: ab
create thread PeakWorkingSetSize: 9592832, WorkingSetSize: 9560064
found 0 folders, size 0, db search time taken: 0.000003 seconds
found 0 files, size 0, db search time taken: 0.000002 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000228 seconds
search 'abc' filter ''
term 0072ce30, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: abc
create thread PeakWorkingSetSize: 9592832, WorkingSetSize: 9560064
found 0 folders, size 0, db search time taken: 0.000003 seconds
found 0 files, size 0, db search time taken: 0.000001 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000814 seconds
WM_ACTIVATE 00000000 00000000, lastfocus 0054065e, current focus 0054065e

Quit, then go back to 644 & the same thing happens:

Code: Select all

WM_ACTIVATE 00000000 00000000, lastfocus 00250318, current focus 00250318
WM_ACTIVATE 00000001 00000000, lastfocus 00250318, current focus 00000000
search 'a' filter ''
term 006f7790, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: a
found 0 folders, size 0, db search time taken: 0.000014 seconds
found 0 files, size 0, db search time taken: 0.000007 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000146 seconds
search 'ab' filter ''
term 007a33b0, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: ab
found 0 folders, size 0, db search time taken: 0.000004 seconds
found 0 files, size 0, db search time taken: 0.000001 seconds
_DB_WAIT: db_get_result_count waiting...
_DB_WAIT: db_get_result_count waited 0.000269 seconds
search 'abc' filter ''
term 006f7768, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: abc
found 0 folders, size 0, db search time taken: 0.000003 seconds
found 0 files, size 0, db search time taken: 0.000002 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000152 seconds
WM_ACTIVATE 00000000 00000000, lastfocus 00250318, current focus 00250318

Quit, then run 644 As Administrator, it then works correctly:

Code: Select all

WM_ACTIVATE 00000000 00000000, lastfocus 00230230, current focus 00230230
WM_ACTIVATE 00000001 00000000, lastfocus 00230230, current focus 00000000
search 'a' filter ''
term 00629db0, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: a
found 44377 folders, size 197052, db search time taken: 0.007289 seconds
found 215211 files, size 918616, db search time taken: 0.020492 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000192 seconds
search 'ab' filter ''
term 0431f058, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: ab
_DB_WAIT: db_get_result_count waiting...
found 1854 folders, size 65812, db search time taken: 0.012507 seconds
found 11273 files, size 65852, db search time taken: 0.031124 seconds
_DB_WAIT: db_get_result_count waited 0.043844 seconds
search 'abc' filter ''
term 04322830, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: abc
found 67 folders, size 65808, db search time taken: 0.006440 seconds
found 279 files, size 65808, db search time taken: 0.024569 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000294 seconds
WM_ACTIVATE 00000000 00000000, lastfocus 00230230, current focus 00230230

Quit, then run 644 again, but not as Admin, & it still works.

Code: Select all

WM_ACTIVATE 00000000 00000000, lastfocus 003d0272, current focus 003d0272
WM_ACTIVATE 00000001 00000000, lastfocus 003d0272, current focus 00000000
search 'a' filter ''
term 002c7790, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: a
found 44377 folders, size 197052, db search time taken: 0.007503 seconds
found 215211 files, size 918616, db search time taken: 0.027358 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000190 seconds
search 'ab' filter ''
term 00355e10, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: ab
_DB_WAIT: db_get_result_count waiting...
found 1854 folders, size 65812, db search time taken: 0.012059 seconds
found 11273 files, size 65852, db search time taken: 0.033993 seconds
_DB_WAIT: db_get_result_count waited 0.046218 seconds
search 'abc' filter ''
term 03cf6d30, flags: 0144, next: 00000000, notnext: 00000000
folderop: 10, fileop: 10, term: abc
found 67 folders, size 65808, db search time taken: 0.008248 seconds
found 279 files, size 65808, db search time taken: 0.022819 seconds
_DB_WAIT: _db_ready_proc waiting...
_DB_WAIT: _db_ready_proc waited 0.000202 seconds
WM_ACTIVATE 00000000 00000000, lastfocus 003d0272, current focus 003d0272

Quit, run 645 As Admin, & it worked.

Pretty sure the very first time I put 645 in & ran it, it too only gave me "3 objects".
And then multiple times thereafter, regardless of how I tried to run it, it only returned "3 objects".
Wasn't until I went back to 644 & messed around with that, that at some point 645 then ran correctly?

And now 645 also is indexing correctly - without the need to Run As Admin?
Originally that was not the case?

Originally I could not get anything in 645 except for "3 objects"?

[void]

When the index is created without admin privileges only the 3 root folders will be index.
When the index is created with admin privileges all files and folders are indexed normally.

However, when changing the privileges in 645b the index is not recreated like in previous versions.

If you created an index with admin privileges and run Everything without admin privileges the index that was created with admin privileges will load, but the monitors will fail to start.

-or-

If you created an index without admin privileges and run Everything with admin privileges only the 3 root folders will show in the index!

I would consider this a bug in 645b.
645 should re-check the USN Journal state each time it loads the index.

The reason for the change was to stop continuous re-indexing bugs when the USN Journal failed to be created.

Thanks for bringing this to my attention.