Crash - error 390
Re: Crash - error 390
Also, I note there is still an xyplorer.exe process in task manager after the crash, have to terminate that manually. I've done this both before and after the dlog test, so the phantom process does not seem to affect the dlog output.
-
- Site Admin
- Posts: 60558
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Crash - error 390
1) Still the same error message??? That's pretty impossible.
2) No error here.
3) When you say crash, you mean error message, or XY going down?
2) No error here.
3) When you say crash, you mean error message, or XY going down?
FAQ | XY News RSS | XY Twitter
Re: Crash - error 390
Actually, there is now no error dialog, just the XY window goes away (crash?) but yet, an xyplorer.exe proccess remains, which has to be terminated (launching XY again without doing so results in two xyplorer.exe processes running).
So, build 0016 does eliminate the error dialog, but does not seem to resolve the crash (or the window disappearing).
So, build 0016 does eliminate the error dialog, but does not seem to resolve the crash (or the window disappearing).
-
- Site Admin
- Posts: 60558
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Crash - error 390
No wonder there was nothing in the debug logs. Something else, far more destructive is going on. The error system itself is among the victims. At the moment I cannot do anything. I will go back to the previous state (0015), and leave it at that.
FAQ | XY News RSS | XY Twitter
Re: Crash - error 390
I find it strange you choose to block smartscreen at the firewall, instead of just disabling it.
Re: Crash - error 390
I think the other way, why not enabling the smart screen in the firewall.
Its enabled by default.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3447)
Portable XYplorer (actual version, including betas)
Everything 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73
Portable XYplorer (actual version, including betas)
Everything 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73
Re: Crash - error 390
I'm in the Insider program, I get new Dev builds regularly, and Windows seems to turn it back on with every update. The entire Defender subsystem seems to constantly be changing settings you try to override, hey look at that, Microsoft doing us a favor
-
- Posts: 224
- Joined: 29 Sep 2022 14:20
- Location: Win10 @125%
Re: Crash - error 390
this is accurate. not on insider; however, i am constantly forced to review my settings after each "patch tuesday" or "out-of-band" update to see which update(s) or setting(s) that were initially disabled, re-enabled again. running WPD and/or ShutUp10 will show several settings re-enabled "for my convenience". at least with WFC, the firewall rules are not reset.
speaking about the mark-of-the-web, is that an attribute that XY can "see" so that a color filter could be applied ? possibly make the file name RED if the downloaded file hasn't been unblocked.
Re: Crash - error 390
That is not a simple attribute.GreetingsFromPoland wrote: ↑08 Mar 2023 18:13 ...
speaking about the mark-of-the-web, is that an attribute that XY can "see" so that a color filter could be applied ? possibly make the file name RED if the downloaded file hasn't been unblocked.
The info is stored inside the file as ADS stream named
:Zone.Identifier
So XY would have to try reading this stream on every file displayed.
Windows 11 Home x64 Version 23H2 (OS Build 22631.3447)
Portable XYplorer (actual version, including betas)
Everything 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73
Portable XYplorer (actual version, including betas)
Everything 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73