Locked WSJT-X wont open after WIN 10 Update Event Log added #FT8 #WSJTX_config


Randy Hansen
 

Log Name:      Application
Source:        Application Error
Date:          11/18/17 15:28:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LAPTOP-FJTE9TL0
Description:
Faulting application name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Faulting module name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Exception code: 0xc0000005
Fault offset: 0x000663be
Faulting process id: 0x23f8
Faulting application start time: 0x01d360b434f761d3
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WSJT\wsjtx\bin\wsjtx.exe
Report Id: c01c0723-364e-4551-b0ac-1394d7627fa9
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-11-18T21:28:42.578597300Z" />
    <EventRecordID>8260</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LAPTOP-FJTE9TL0</Computer>
    <Security />
  </System>
  <EventData>
    <Data>wsjtx.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>59f4c04d</Data>
    <Data>wsjtx.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>59f4c04d</Data>
    <Data>c0000005</Data>
    <Data>000663be</Data>
    <Data>23f8</Data>
    <Data>01d360b434f761d3</Data>
    <Data>C:\WSJT\wsjtx\bin\wsjtx.exe</Data>
    <Data>C:\WSJT\wsjtx\bin\wsjtx.exe</Data>
    <Data>c01c0723-364e-4551-b0ac-1394d7627fa9</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>


Bill Somerville
 

On 18/11/2017 22:13, Randy Hansen wrote:
Log Name:      Application
Source:        Application Error
Date:          11/18/17 15:28:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LAPTOP-FJTE9TL0
Description:
Faulting application name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Faulting module name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Exception code: 0xc0000005
Fault offset: 0x000663be
Faulting process id: 0x23f8
Faulting application start time: 0x01d360b434f761d3
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WSJT\wsjtx\bin\wsjtx.exe
Report Id: c01c0723-364e-4551-b0ac-1394d7627fa9
Hi Randy,

this seems to be a Microsoft defect. Are you using Windows 10 Pro? I ask because the only other report so far was from a user using that.

Although it is not recommended, you can start WSJT-X by using "Run as Administrator", I have no idea why that is necessary. The error is a memory access violation and should not be happening.

I suggest you report the issue to Microsoft as there is not much we can do to diagnose or resolve this issue.

73
Bill
G4WJS.


Randy Hansen
 

I am using Microsoft Pro 10.  I found a work around by using "trouble shoot compatibility",  When you select "test program" it will open.  Am I the only one who has a problem?  

Virus-free. www.avast.com

On Sat, Nov 18, 2017 at 7:00 PM, Bill Somerville <g4wjs@...> wrote:
On 18/11/2017 22:13, Randy Hansen wrote:
Log Name:      Application
Source:        Application Error
Date:          11/18/17 15:28:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LAPTOP-FJTE9TL0
Description:
Faulting application name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Faulting module name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Exception code: 0xc0000005
Fault offset: 0x000663be
Faulting process id: 0x23f8
Faulting application start time: 0x01d360b434f761d3
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WSJT\wsjtx\bin\wsjtx.exe
Report Id: c01c0723-364e-4551-b0ac-1394d7627fa9

Hi Randy,

this seems to be a Microsoft defect. Are you using Windows 10 Pro? I ask because the only other report so far was from a user using that.

Although it is not recommended, you can start WSJT-X by using "Run as Administrator", I have no idea why that is necessary. The error is a memory access violation and should not be happening.

I suggest you report the issue to Microsoft as there is not much we can do to diagnose or resolve this issue.

73
Bill
G4WJS.






Bill Somerville
 

Hi Randy,

can you right click the wsjtx.exe application and select "Properties" then the "Compatibility" tab and send me a screen capture of the settings please?

73
Bill
G4WJS.

On 19/11/2017 02:04, Randy Hansen wrote:

I am using Microsoft Pro 10.  I found a work around by using "trouble shoot compatibility",  When you select "test program" it will open.  Am I the only one who has a problem?  

Virus-free. www.avast.com

On Sat, Nov 18, 2017 at 7:00 PM, Bill Somerville <g4wjs@...> wrote:
On 18/11/2017 22:13, Randy Hansen wrote:
Log Name:      Application
Source:        Application Error
Date:          11/18/17 15:28:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LAPTOP-FJTE9TL0
Description:
Faulting application name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Faulting module name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Exception code: 0xc0000005
Fault offset: 0x000663be
Faulting process id: 0x23f8
Faulting application start time: 0x01d360b434f761d3
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WSJT\wsjtx\bin\wsjtx.exe
Report Id: c01c0723-364e-4551-b0ac-1394d7627fa9

Hi Randy,

this seems to be a Microsoft defect. Are you using Windows 10 Pro? I ask because the only other report so far was from a user using that.

Although it is not recommended, you can start WSJT-X by using "Run as Administrator", I have no idea why that is necessary. The error is a memory access violation and should not be happening.

I suggest you report the issue to Microsoft as there is not much we can do to diagnose or resolve this issue.

73
Bill
G4WJS.



Randy Hansen
 
Edited

its working now but here is the screen shot 



On Sat, Nov 18, 2017 at 8:15 PM, Bill Somerville <g4wjs@...> wrote:
Hi Randy,

can you right click the wsjtx.exe application and select "Properties" then the "Compatibility" tab and send me a screen capture of the settings please?

73
Bill
G4WJS.

On 19/11/2017 02:04, Randy Hansen wrote:
I am using Microsoft Pro 10.  I found a work around by using "trouble shoot compatibility",  When you select "test program" it will open.  Am I the only one who has a problem?  

Virus-free. www.avast.com

On Sat, Nov 18, 2017 at 7:00 PM, Bill Somerville <g4wjs@...> wrote:
On 18/11/2017 22:13, Randy Hansen wrote:
Log Name:      Application
Source:        Application Error
Date:          11/18/17 15:28:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LAPTOP-FJTE9TL0
Description:
Faulting application name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Faulting module name: wsjtx.exe, version: 0.0.0.0, time stamp: 0x59f4c04d
Exception code: 0xc0000005
Fault offset: 0x000663be
Faulting process id: 0x23f8
Faulting application start time: 0x01d360b434f761d3
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WSJT\wsjtx\bin\wsjtx.exe
Report Id: c01c0723-364e-4551-b0ac-1394d7627fa9

Hi Randy,

this seems to be a Microsoft defect. Are you using Windows 10 Pro? I ask because the only other report so far was from a user using that.

Although it is not recommended, you can start WSJT-X by using "Run as Administrator", I have no idea why that is necessary. The error is a memory access violation and should not be happening.

I suggest you report the issue to Microsoft as there is not much we can do to diagnose or resolve this issue.

73
Bill
G4WJS.