Looks for all the world that the newly created Standard User corrupted the file I tested with.
You should become familiar with Process Monitor and start a capture running, then attempt to do your file open tests. See if you can see whether the application
is starting or not, or it is a failure to launch that is happening. The File menu
has an icon, marking the thing that "stops" a trace and the Edit menu has a "clear" when you want to wipe the trace and do another/fresh trace.
https://learn.microsoft.com/en-us/answers/questions/760616/process-monitor-on-windows-7-sysinternals-system-r
Process Monitor v3.84 is the last version that supports Vista and 7.
Here's the link:
https://web.archive.org/web/20210820090300/https://download.sysinternals.com/files/ProcessMonitor.zip
Paul wrote:
[snip]
.
Looks for all the world that the newly created Standard User corrupted the file I tested with.
OP here ...
So I tried copying the suspect file to a NAS on the same LAN.-a I used Robocopy so I could generate a log file.-a It hangs.-a The same using Copy.
You should become familiar with Process Monitor and start a capture running, >> then attempt to do your file open tests. See if you can see whether the application
is starting or not, or it is a failure to launch that is happening. The File menu
has an icon, marking the thing that "stops" a trace and the Edit menu has a >> "clear" when you want to wipe the trace and do another/fresh trace.
https://learn.microsoft.com/en-us/answers/questions/760616/process-monitor-on-windows-7-sysinternals-system-r
-a-a-a-a Process Monitor v3.84 is the last version that supports Vista and 7.
-a-a-a-a Here's the link:
-a-a-a-a https://web.archive.org/web/20210820090300/https://download.sysinternals.com/files/ProcessMonitor.zip
Downloaded and installed.
Procmon.exe immediately reports "Unable to load Process Monitor device driver."
Procmon64.exe reports the same (this is a 64-bit system).
Procmon64a.exe reports that it is not a valid Win32 app.
Does this suggest that there is something more seriously broken?
[snip good stuff about running traces]
Procmon.exe immediately reports "Unable to load Process Monitor device driver."
Procmon64.exe reports the same (this is a 64-bit system).
Procmon64a.exe reports that it is not a valid Win32 app.
Does this suggest that there is something more seriously broken?
[snip good stuff about running traces]
Procmon64a is the ARM architecture version, for running on a Qualcomm laptop maybe.
I hope you've had a chance to scan the box, for malware. I hardly ever get any
"evidence" this way, but it's a step worth taking as some day, we'll actually catch something. It could happen.
You can do the same thing from the Command Prompt.
copy a b
and specify absolute paths for the "a" item and what you want
when it is stored somewhere else. That probably starts a subshell,
but it might not go near explorer.exe while it runs. That would be
roughly the same as writing your own copy program.
I will try Procmon64.exe with AVG disabled.
Graham J wrote:
[snip]
OP here ...
I will try Procmon64.exe with AVG disabled.
No improvement.
[snip]
Graham J <nobody@nowhere.co.uk> wrote in news:11bfu8h$1tt62$1@dont-email.me:
Graham J wrote:
[snip]
OP here ...
I will try Procmon64.exe with AVG disabled.
No improvement.
[snip]
Perhaps try a CHKDSK with the appropriate recovery options on. That might show a file or two left unindexed and causing problems.
Perhaps try a CHKDSK with the appropriate recovery options on. That might >> show a file or two left unindexed and causing problems.
Paul wrote:might
[snip]
Perhaps try a CHKDSK with the appropriate recovery options on. That
show a file or two left unindexed and causing problems.
chkdsk /f C:
0 bad file records processed.
2 EA records processed.
191 reparse records processed.
0 unindexed files recovered.
Cleaning up 1312 unused index entries from index $SII of file 0x9.
Cleaning up 1312 unused index entries from index $SDH of file 0x9.
Cleaning up 1312 unused security descriptors.
Login as Admin
Explorer right-click and double-click on the test files now works.
Logoff
Login as Standard User
Explorer right-click shows menu but any option there selected hangs.
Explorer double-click on .docx file starts Word but then hangs
Quit Word
Open Word - wants safe mode
Logoff
Login as Admin
Explorer right-click and double-click on the test files both fail
Word hangs, quit and invoke Word again, wants safe mode.
I have seen this sequence of symptoms before.
Reboot, login as Admin
Explorer right-click and double-click on the test files now works.
So the reboot does allow Admin to work normally
Make completely new Standard User account "NewUser"
Logoff
Login NewUser
Configure Word for first use
Explorer right-click test files fails, exactly as seen with the previous Standard user. Did not try to use Word.
Logoff
Login as Admin
Explorer right-click and double-click on the test files works OK.
It looks like there is something corrupt in the default profile which propagates to any new Standard User account.
Ideas please?
Paul wrote:
[snip]
Perhaps try a CHKDSK with the appropriate recovery options on.-a That might >>> show a file or two left unindexed and causing problems.
chkdsk /f C:
0 bad file records processed.
2 EA records processed.
191 reparse records processed.
0 unindexed files recovered.
Cleaning up 1312 unused index entries from index $SII of file 0x9.
Cleaning up 1312 unused index entries from index $SDH of file 0x9.
Cleaning up 1312 unused security descriptors.
Login as Admin
Explorer right-click and double-click on the test files now works.
Logoff
Login as Standard User
Explorer right-click shows menu but any option there selected hangs.
Explorer double-click on .docx file starts Word but then hangs
Quit Word
Open Word - wants safe mode
Logoff
Login as Admin
Explorer right-click and double-click on the test files both fail
Word hangs, quit and invoke Word again, wants safe mode.
I have seen this sequence of symptoms before.
Reboot, login as Admin
Explorer right-click and double-click on the test files now works.
So the reboot does allow Admin to work normally
Make completely new Standard User account "NewUser"
Logoff
Login NewUser
Configure Word for first use
Explorer right-click test files fails, exactly as seen with the previous Standard user.-a Did not try to use Word.
Logoff
Login as Admin
Explorer right-click and double-click on the test files works OK.
It looks like there is something corrupt in the default profile which propagates to any new Standard User account.
Ideas please?
Do you have any scripting options on? Perhaps something attacked or
modified (whatever it's called) that provides more commands to a user
beyond the normal.
Would any of that be related to the just discovered PHP hack?
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 55:40:46 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,687 |