Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped.
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked
on the icon the desktop the little blue circle would be there for a few seconds. If I clicked where it's pinned to the taskbar nothing at all happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that.
Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I
run Everything and search for Agent, but I can't find them now. :-(
Then last night, after restarting windows, but NOT s eeing any system updates, the version on my laptop, the version I use every day, stopped working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name
of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
More of the error message
agent.exe
1.93.576.0
b2102d91
StackHash_5c80
0.0.0.0
00000000
c000041d
PCH_62_FROM_unknown+0x00000000
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CF.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4847.tmp.WERInternalMet adata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4887.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4905.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_agent.ex e_64e4de5a5aebae741324eb1e7f58d97035e11111_97409d5f_58a7e5ca-3bdb-463e-8 3c9-8fcc9c5d56e5
0
0a529edb-6436-4d5b-9130-32cd3ff072ec
268435456
86c5cde41c828b9a49b074df4b5fddbf
0
HELP!!!!
Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped.
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked
on the icon the desktop the little blue circle would be there for a few >seconds. If I clicked where it's pinned to the taskbar nothing at all >happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that. >Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I
run Everything and search for Agent, but I can't find them now. :-(
Then last night, after restarting windows, but NOT s eeing any system >updates, the version on my laptop, the version I use every day, stopped >working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name
of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
More of the error message
agent.exe
1.93.576.0
b2102d91
StackHash_5c80
0.0.0.0
00000000
c000041d
PCH_62_FROM_unknown+0x00000000
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CF.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4847.tmp.WERInternalMet >adata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4887.tmp.xml >\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A6.tmp.csv >\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4905.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_agent.ex >e_64e4de5a5aebae741324eb1e7f58d97035e11111_97409d5f_58a7e5ca-3bdb-463e-8 >3c9-8fcc9c5d56e5
0
0a529edb-6436-4d5b-9130-32cd3ff072ec
268435456
86c5cde41c828b9a49b074df4b5fddbf
0
HELP!!!!
On 8/25/2023 1:02 AM, Micky wrote:
Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped.
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked
on the icon the desktop the little blue circle would be there for a few
seconds. If I clicked where it's pinned to the taskbar nothing at all
happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that.
Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I
run Everything and search for Agent, but I can't find them now. :-(
Then last night, after restarting windows, but NOT s eeing any system
updates, the version on my laptop, the version I use every day, stopped
working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name
of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
More of the error message
agent.exe
1.93.576.0
b2102d91
StackHash_5c80
0.0.0.0
00000000
c000041d
PCH_62_FROM_unknown+0x00000000
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CF.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4847.tmp.WERInternalMet
adata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4887.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4905.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_agent.ex
e_64e4de5a5aebae741324eb1e7f58d97035e11111_97409d5f_58a7e5ca-3bdb-463e-8
3c9-8fcc9c5d56e5
0
0a529edb-6436-4d5b-9130-32cd3ff072ec
268435456
86c5cde41c828b9a49b074df4b5fddbf
0
HELP!!!!
I would use this first one. It installed just fine in a Win10 VM.
These are from my collection (the collection gathered from questions).
Name: a32en193__forte_free_agent_mirrors_easynews_com.exe
Size: 2,405,565 bytes (2349 KiB)
SHA256: B7CFF20A784D61968C7B297CE64B14B4C702623CE7B9DAF307D335DB87EB5FDD
Name: a16en193__forte_free_agent_mirrors_easynews_com.exe
Size: 2,548,809 bytes (2489 KiB)
SHA256: 56EDBBD25B81F5A64C3A364F734AAE461E77EDA2136AD5E46F030BBB030EB34B
*******
"The StackHash error occurs when DEP is invoked and has an issue with
whatever application youβre trying to run (and there are several hundred
out there that seem to give it fits). The error is related to
Data Execution Prevention."
"Exception 0xC000041D means that an unhandled exception was encountered
during a user callback. It means that 0xC000041D is a second chance exception.
So we should capture the first chance exception, if we want to know the root cause" <Hah>
And I think that might happen, if memory that is mapped as being for data, someone tries to execute it as program code.
I can't find a reasonable recipe right now, to fix that.
You can do an offline scan. The pictorial summary...
https://www.tenforums.com/attachments/tutorials/284639d1592839239-how-run-microsoft-defender-offline-scan-windows-10-a-microsoft_defender_offline_scan-3.png
Full recipe.
https://www.tenforums.com/tutorials/42305-how-run-microsoft-defender-offline-scan-windows-10-a.html
I don't know if that'll remove something, or you'll need sfc /scannow and friends.
I've seen DEP problems before. My old, defenseless WinXP had that once.
While DEP is opt-in or opt-out, I don't recommend removing it
just so you can "avoid" that error.
That error is a *warning*.
On Fri, 25 Aug 2023 05:02:24 GMT, "Micky" <NONONOmisc07@fmguy.com>
wrote:
Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped.
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked
on the icon the desktop the little blue circle would be there for a few
seconds. If I clicked where it's pinned to the taskbar nothing at all
happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that.
Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I
run Everything and search for Agent, but I can't find them now. :-(
Then last night, after restarting windows, but NOT s eeing any system
updates, the version on my laptop, the version I use every day, stopped
working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name
of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
More of the error message
agent.exe
1.93.576.0
b2102d91
StackHash_5c80
0.0.0.0
00000000
c000041d
PCH_62_FROM_unknown+0x00000000
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CF.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4847.tmp.WERInternalMet
adata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4887.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4905.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_agent.ex
e_64e4de5a5aebae741324eb1e7f58d97035e11111_97409d5f_58a7e5ca-3bdb-463e-8
3c9-8fcc9c5d56e5
0
0a529edb-6436-4d5b-9130-32cd3ff072ec
268435456
86c5cde41c828b9a49b074df4b5fddbf
0
HELP!!!!
The other post by Paul probably is more useful than this will be.
I use Windows Defender. Some time back, something happened to cause it
to flag 32-bit Windows exectables as viruses. This were files inside a program development repository, ie, files that have been there for
decades and (as it kept picking on them) clearly get rebuilt as
needed. Windows Defender then branched out to claim files in my old
C++ exploratory directories -- files untouched for 15 years or so --
were affected.
My point is that, if you are using Windows Defender, you aren't just
getting major system updates. Windows Defender updates quite often.
Also, I take it you have tried right-clicking (or left-clicking if you
are left-handed) on the Agent icon and selecting "Open"? And, if the
desktop icon is a shortcut, that you have found the executable and
tried to run that directly?
Not that I expect either of these to help, but Win10 is getting
weirder and weirder so who can say?
On Fri, 25 Aug 2023 03:12:53 -0400, Paul wrote:
On 8/25/2023 1:02 AM, Micky wrote:
Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped.
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked
on the icon the desktop the little blue circle would be there for a few
seconds. If I clicked where it's pinned to the taskbar nothing at all
happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that.
Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I
run Everything and search for Agent, but I can't find them now. :-(
Then last night, after restarting windows, but NOT s eeing any system
updates, the version on my laptop, the version I use every day, stopped
working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name
of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
More of the error message
agent.exe
1.93.576.0
b2102d91
StackHash_5c80
0.0.0.0
00000000
c000041d
PCH_62_FROM_unknown+0x00000000
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CF.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4847.tmp.WERInternalMet >>> adata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4887.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4905.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_agent.ex >>> e_64e4de5a5aebae741324eb1e7f58d97035e11111_97409d5f_58a7e5ca-3bdb-463e-8 >>> 3c9-8fcc9c5d56e5
0
0a529edb-6436-4d5b-9130-32cd3ff072ec
268435456
86c5cde41c828b9a49b074df4b5fddbf
0
HELP!!!!
I would use this first one. It installed just fine in a Win10 VM.
These are from my collection (the collection gathered from questions).
Name: a32en193__forte_free_agent_mirrors_easynews_com.exe
Size: 2,405,565 bytes (2349 KiB)
SHA256: B7CFF20A784D61968C7B297CE64B14B4C702623CE7B9DAF307D335DB87EB5FDD
Name: a16en193__forte_free_agent_mirrors_easynews_com.exe
Size: 2,548,809 bytes (2489 KiB)
SHA256: 56EDBBD25B81F5A64C3A364F734AAE461E77EDA2136AD5E46F030BBB030EB34B
*******
"The StackHash error occurs when DEP is invoked and has an issue with
whatever application youβre trying to run (and there are several hundred
out there that seem to give it fits). The error is related to
Data Execution Prevention."
"Exception 0xC000041D means that an unhandled exception was encountered >> during a user callback. It means that 0xC000041D is a second chance exception.
So we should capture the first chance exception, if we want to know the root cause" <Hah>
And I think that might happen, if memory that is mapped as being for data, >> someone tries to execute it as program code.
According to the OP's other post <http://al.howardknight.net/?ID=169299317900>,
both Agent 1.93 and Agent 4 are affected.
Agent 1.93 is not compatible with DEP for applications.
But Agent 4 is compatible with DEP for applications.
If one tries to run Agent 1.93 when DEP is enabled for applications
including Agent 1.93, one will get an exception code 0xc000041d
and Agent 1.93 will not run. Agent 4 is not affected.
Agent 1.93 was built with Borland OWL which used thunk blocks
allocated on the heap and containing dynamically-created code
to be executed. Agent 4 was not built with Borland OWL.
I can't find a reasonable recipe right now, to fix that.
If the problem were caused by DEP, then...
Either, turn on DEP for essential Windows progams and services only.
Or, add Agent 1.93 to the list of exclusions.
screen-shot: <http://img4.imagetitan.com/img.php?image=26_uc9k9m_1__data_execution_prevention_options.png>
OTOH the inclusion of Agent 4 in the OP's other post might
suggest this is not DEP.
REF: <http://al.howardknight.net/?ID=169299317900>
You can do an offline scan. The pictorial summary...
https://www.tenforums.com/attachments/tutorials/284639d1592839239-how-run-microsoft-defender-offline-scan-windows-10-a-microsoft_defender_offline_scan-3.png
Full recipe.
https://www.tenforums.com/tutorials/42305-how-run-microsoft-defender-offline-scan-windows-10-a.html
I don't know if that'll remove something, or you'll need sfc /scannow and friends.
I've seen DEP problems before. My old, defenseless WinXP had that once.
While DEP is opt-in or opt-out, I don't recommend removing it
just so you can "avoid" that error.
One does not need to turn off DEP. There are other options
Either, turn on DEP for essential Windows progams and services only.
Or, add Agent 1.93 to the list of exclusions.
screen-shot: <http://img4.imagetitan.com/img.php?image=26_uc9k9m_1__data_execution_prevention_options.png>
To find these options in Windows 10
1. Go to Start >> Settings >> System >> About
2. At the right, click "Advanced system settings"
3. Select the "Advanced" tab and in the "Performance" box, click
"Settings"
4. Select the tab "Data Execution Prevention"
That error is a *warning*.
For Agent 1.93 DEP is a hard error which totally stops Agent 1.93
from running.
wmic OS Get DataExecutionPrevention_SupportPolicy
On 8/25/2023 11:55 AM, Paul S Person wrote:
On Fri, 25 Aug 2023 05:02:24 GMT, "Micky" <NONONOmisc07@fmguy.com>
wrote:
Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped.
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked
on the icon the desktop the little blue circle would be there for a few
seconds. If I clicked where it's pinned to the taskbar nothing at all
happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that. >>> Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I
run Everything and search for Agent, but I can't find them now. :-(
Then last night, after restarting windows, but NOT s eeing any system
updates, the version on my laptop, the version I use every day, stopped
working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name
of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
More of the error message
agent.exe
1.93.576.0
b2102d91
StackHash_5c80
0.0.0.0
00000000
c000041d
PCH_62_FROM_unknown+0x00000000
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CF.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4847.tmp.WERInternalMet >>> adata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4887.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4905.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_agent.ex >>> e_64e4de5a5aebae741324eb1e7f58d97035e11111_97409d5f_58a7e5ca-3bdb-463e-8 >>> 3c9-8fcc9c5d56e5
0
0a529edb-6436-4d5b-9130-32cd3ff072ec
268435456
86c5cde41c828b9a49b074df4b5fddbf
0
HELP!!!!
The other post by Paul probably is more useful than this will be.
I use Windows Defender. Some time back, something happened to cause it
to flag 32-bit Windows exectables as viruses. This were files inside a
program development repository, ie, files that have been there for
decades and (as it kept picking on them) clearly get rebuilt as
needed. Windows Defender then branched out to claim files in my old
C++ exploratory directories -- files untouched for 15 years or so --
were affected.
My point is that, if you are using Windows Defender, you aren't just
getting major system updates. Windows Defender updates quite often.
Also, I take it you have tried right-clicking (or left-clicking if you
are left-handed) on the Agent icon and selecting "Open"? And, if the
desktop icon is a shortcut, that you have found the executable and
tried to run that directly?
Not that I expect either of these to help, but Win10 is getting
weirder and weirder so who can say?
On Fri, 25 Aug 2023 17:46:05 -0400, Paul <nospam@needed.invalid>
wrote:
On 8/25/2023 11:55 AM, Paul S Person wrote:
On Fri, 25 Aug 2023 05:02:24 GMT, "Micky" <NONONOmisc07@fmguy.com>
wrote:
Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped. >>>>
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked >>>> on the icon the desktop the little blue circle would be there for a few >>>> seconds. If I clicked where it's pinned to the taskbar nothing at all >>>> happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that. >>>> Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I >>>> run Everything and search for Agent, but I can't find them now. :-( >>>>
Then last night, after restarting windows, but NOT s eeing any system
updates, the version on my laptop, the version I use every day, stopped >>>> working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name >>>> of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
More of the error message
agent.exe
1.93.576.0
b2102d91
StackHash_5c80
0.0.0.0
00000000
c000041d
PCH_62_FROM_unknown+0x00000000
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER46CF.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4847.tmp.WERInternalMet >>>> adata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4887.tmp.xml >>>> \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER48A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4905.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_agent.ex >>>> e_64e4de5a5aebae741324eb1e7f58d97035e11111_97409d5f_58a7e5ca-3bdb-463e-8 >>>> 3c9-8fcc9c5d56e5
0
0a529edb-6436-4d5b-9130-32cd3ff072ec
268435456
86c5cde41c828b9a49b074df4b5fddbf
0
HELP!!!!
The other post by Paul probably is more useful than this will be.
I use Windows Defender. Some time back, something happened to cause it
to flag 32-bit Windows exectables as viruses. This were files inside a
program development repository, ie, files that have been there for
decades and (as it kept picking on them) clearly get rebuilt as
needed. Windows Defender then branched out to claim files in my old
C++ exploratory directories -- files untouched for 15 years or so --
were affected.
My point is that, if you are using Windows Defender, you aren't just
getting major system updates. Windows Defender updates quite often.
Also, I take it you have tried right-clicking (or left-clicking if you
are left-handed) on the Agent icon and selecting "Open"? And, if the
desktop icon is a shortcut, that you have found the executable and
tried to run that directly?
Not that I expect either of these to help, but Win10 is getting
weirder and weirder so who can say?
<snippo explanation of DEP>
1. DEP can be restricted to sytem only. I checked mine and that is how
it is set here. Not that that is relevant to anything.
2. Even if it is allowed for everything, specific items can be
excepted.
3. So Win10 does actually have a great deal of control over DEP. Or,
at least, it claims have it. There's reality, and then there's Win10.
Just because I am only aware of Windows Defender updates doesn't mean
that those are the /only/ not-system-updates being received. Something
on the OPs computers appears to have changed, and it might be a
Windows subsystem whose updates aren't system updates.
Or it may just be that Win10 is now be pretending to itself that DEP
applies to all files, without regard to what the user wants.
Kind of like how it starting pretending to itself, some time back,
that I wanted it to require me to do Ctl-Alt-Del before being
graciously permitted to enter my password. I've tried the online help.
The best I managed is that now it reminds me of the requirement on the
screen before the log in screen.
But only on the mainframe with the AMD processor. The laptop with the
Intel processor doesn't care.
As I have said, Win10 is just getting weirder and weirder.
wmic OS Get DataExecutionPrevention_SupportPolicy
In my reply to Ralph, I found this.
wmic OS Get DataExecutionPrevention_SupportPolicy
DataExecutionPrevention_SupportPolicy
2
0 DEP is disabled for all processes.
1 DEP is enabled for all processes.
2 DEP is enabled for only Windows system components and services. <===
And that's for the test VM where I tested Forte 1.93.
That seems to be the default chosen by Microsoft in my case.
I don't know if this policy varies at all or not.
I'm typing this on Windows 11 Home, and the value is "2" also.
Perhaps a third-party AV can change the value ?
On Sat, 26 Aug 2023 13:45:00 -0400, Paul <nospam@needed.invalid> wrote:
In my reply to Ralph, I found this.
wmic OS Get DataExecutionPrevention_SupportPolicy
DataExecutionPrevention_SupportPolicy
2
0 β DEP is disabled for all processes.
1 β DEP is enabled for all processes.
2 β DEP is enabled for only Windows system components and services. <===
And that's for the test VM where I tested Forte 1.93.
That seems to be the default chosen by Microsoft in my case.
I don't know if this policy varies at all or not.
I'm typing this on Windows 11 Home, and the value is "2" also.
Perhaps a third-party AV can change the value ?
I would expect the DEP control in the GUI to match what you see with powershell.
Is that not always the case?
On 8/26/2023 2:23 PM, Char Jackson wrote:
On Sat, 26 Aug 2023 13:45:00 -0400, Paul <nospam@needed.invalid> wrote:
In my reply to Ralph, I found this.
wmic OS Get DataExecutionPrevention_SupportPolicy
DataExecutionPrevention_SupportPolicy
2
0 DEP is disabled for all processes.
1 DEP is enabled for all processes.
2 DEP is enabled for only Windows system components and services. <=== >>>
And that's for the test VM where I tested Forte 1.93.
That seems to be the default chosen by Microsoft in my case.
I don't know if this policy varies at all or not.
I'm typing this on Windows 11 Home, and the value is "2" also.
Perhaps a third-party AV can change the value ?
I would expect the DEP control in the GUI to match what you see with powershell.
Is that not always the case?
That's just the first Google hit I found, on how to check it.
On some older Windows OSes, DEP may have been a "boot line" option.
But only on the mainframe with the AMD processor. The laptop with the
Intel processor doesn't care.
On Sat, 26 Aug 2023 09:04:16 -0700, Paul S Person ><psperson@old.netcom.invalid> wrote:
But only on the mainframe with the AMD processor. The laptop with the
Intel processor doesn't care.
A mainframe with an AMD processor? What mainframe is that?
1. DEP can be restricted to sytem only. I checked mine and that is how
it is set here. Not that that is relevant to anything.
2. Even if it is allowed for everything, specific items can be
excepted.
3. So Win10 does actually have a great deal of control over DEP. Or,
at least, it claims have it. There's reality, and then there's Win10.
Just because I am only aware of Windows Defender updates doesn't mean
that those are the /only/ not-system-updates being received. Something
on the OPs computers appears to have changed, and it might be a
Windows subsystem whose updates aren't system updates.
Or it may just be that Win10 is now be pretending to itself that DEP
applies to all files, without regard to what the user wants.
On Sun, 27 Aug 2023 07:49:05 -0700, Ken Blake <Ken@invalid.news.com>
wrote:
On Sat, 26 Aug 2023 09:04:16 -0700, Paul S Person >><psperson@old.netcom.invalid> wrote:
But only on the mainframe with the AMD processor. The laptop with the >>>Intel processor doesn't care.
A mainframe with an AMD processor? What mainframe is that?
An HP Envy. I'm using "mainframe" here as opposed to "laptop".
I suppose "desktop" would be a more conventional description.
But I think of it as /my/ mainframe. It is certainly my main computer.
On Sat, 26 Aug 2023 09:04:16 -0700, Paul S Person wrote:
1. DEP can be restricted to sytem only. I checked mine and that is how
it is set here. Not that that is relevant to anything.
2. Even if it is allowed for everything, specific items can be
excepted.
3. So Win10 does actually have a great deal of control over DEP. Or,
at least, it claims have it. There's reality, and then there's Win10.
Just because I am only aware of Windows Defender updates doesn't mean
that those are the /only/ not-system-updates being received. Something
on the OPs computers appears to have changed, and it might be a
Windows subsystem whose updates aren't system updates.
Or the problem may not be caused by DEP. The OP's other post [1] said
that both Agent 1.93 and Agent 4 were affected. Agent 4 is compatible
with DEP.
Or it may just be that Win10 is now be pretending to itself that DEP
applies to all files, without regard to what the user wants.
I am also running Win10, fully updated. My DEP settings are, turned
on for system only. DEP does not apply to all files; Agent 1.93 still
runs even though Agent 1.93 is not compatible with DEP.
On Fri, 25 Aug 2023 03:12:53 -0400, Paul wrote:
On 8/25/2023 1:02 AM, Micky wrote:
Win10, fully updated, one Pro and one Homet
Agent worked fine until recently and two nights ago, but they stopped.
About 2 weeks ago, it wouldn't even start. I'd click and if I clicked
on the icon the desktop the little blue circle would be there for a few
seconds. If I clicked where it's pinned to the taskbar nothing at all
happened.
Event Viewer calls it an Event 1001, but it calls a lot of things that.
Level 4, APPCRASH
Continuing my story, that was 2 weeks ago. I tried to fix it but
didn't know how to read the error files listed below. (The only text
file is temp and it's gone now.) I also have other error files when I
run Everything and search for Agent, but I can't find them now. :-(
Then last night, after restarting windows, but NOT s eeing any system
updates, the version on my laptop, the version I use every day, stopped
working. It too does nothing when I click on the task bar, except
write an error file
I finally found on the web a post by Ralph that reminded me of the name
of the install file, so I reinstalled Agent 1.93 into the same
locations but no change. It's paid for and registered.
Has something happened to Windows that might have affected both
computers. Can I remedy it.
Right now I had to start using Xananews.
.....
HELP!!!!
I would use this first one. It installed just fine in a Win10 VM.
These are from my collection (the collection gathered from questions).
Name: a32en193__forte_free_agent_mirrors_easynews_com.exe
Size: 2,405,565 bytes (2349 KiB)
SHA256: B7CFF20A784D61968C7B297CE64B14B4C702623CE7B9DAF307D335DB87EB5FDD
Name: a16en193__forte_free_agent_mirrors_easynews_com.exe
Size: 2,548,809 bytes (2489 KiB)
SHA256: 56EDBBD25B81F5A64C3A364F734AAE461E77EDA2136AD5E46F030BBB030EB34B
*******
"The StackHash error occurs when DEP is invoked and has an issue with
whatever application youre trying to run (and there are several hundred >> out there that seem to give it fits). The error is related to
Data Execution Prevention."
"Exception 0xC000041D means that an unhandled exception was encountered >> during a user callback. It means that 0xC000041D is a second chance exception.
So we should capture the first chance exception, if we want to know the root cause" <Hah>
And I think that might happen, if memory that is mapped as being for data, >> someone tries to execute it as program code.
According to the OP's other post <http://al.howardknight.net/?ID=169299317900>,
both Agent 1.93 and Agent 4 are affected.
Agent 1.93 is not compatible with DEP for applications.
But Agent 4 is compatible with DEP for applications.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 129:47:18 |
| Calls: | 6,663 |
| Calls today: | 1 |
| Files: | 12,212 |
| Messages: | 5,335,387 |
