Windows 10 update 1703 crashes in FieldWorks

[Paul Nelson]

Hello,

I met with some friends at Microsoft last Tuesday. If you have experienced the crashes of FieldWorks after updating to Windows build 1703 (Windows Creator's Update) you can help us. By you submitting Feedback on this crash you will encourage Microsoft to fix their bug more quickly.

Microsoft has a "Feedback Hub" tool you can report your crash.

1. Run "Feedback Hub" app 

2. On left column, click on 

3. Click on "+ Add new feedback" button (top right)

4. Fill in information

    a. Choose "Problem"

    b. Fill in your issue and provide detail you are able.

    c. Choose category "Desktop Environment", subcategory "All other issues"

    d. Have Fieldworks running and prepared for a scenario where you crash.

    e. Click "Start capture"

    f. Run your scenario that causes FieldWorks to crash

    g. When FieldWorks has crashed, click "Stop Capture"

    h. Check your information and click "Submit"

Thank you for helping us help Microsoft fix Windows.

Paul

  

[Jonathan Dailey]

I appreciate this.  Shouldn't this problem be listed on the known issues section of the release?

--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+unsubscribe@googlegroups.com.
To post to this group, send email to flex...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/CAJ6OYomyMcO3YRf%3DnshpEZj9N-cN6qcG5PD5vzg4r5VosGi81Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

SIL International

Language Technology Consultant

[Paul Nelson]

The Windows crash is not limited to the latest version. It happens on 8.2.9 as well. This is a Windows bug we should report.

Paul

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/CAApef%3Di_M%2BfDcFADiD0%2BQJdjL5vQkN2VRuw3NHgtO8xXiEYBOQ%40mail.gmail.com.

[Jonathan Dailey]

I have posted my crash.  I wonder if up-voting each other's reports would also be effective?

[Ken Zook]

I think upvoting would be great, but I couldn’t figure out how to do that. If you can send some instructions, maybe everyone could do that without upgrading and then finding Flex seriously broken.

 

There are two known crashes at this point.

1.       Go into an interlinear text in the Analyze tab.

2.       Right-clicking a Sense and adding another sense in the lexicon.

 

Ken

--

[Paul Nelson]

To upvote what others have entered...

1. Open Feedback Hub

2. On left column, click on 

3. Under "All feedback"

    a. Set Sort to "Most recent"

    b. Set Category to "Desktop Environment"

    c. Set Subcategory to "All other issues" (bottom of list)

4. On any bug that mentions Fieldworks, click on the blue "Upvote"

--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+unsubscribe@googlegroups.com.
To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/01210f228fbc33265f02d19bf68d99ed%40mail.gmail.com.

[jim_al...@wycliffe.org]

You have to have windows 10 in order to do this.

J

To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.

To post to this group, send email to flex...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/01210f228fbc33265f02d19bf68d99ed%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

 

--

You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.

To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.

To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/CAJ6OYoneFOTXm80Sv6M9QeYarUbYs%2BSWvH459MMqn0oBQ%3DBkBg%40mail.gmail.com.

[Tim Gaved]

Is the only solution to wait for Microsoft to fix to their bug? I guess the number of FLEx users is a very small proportion of Windows users so we could be waiting a long time! As I only have the Home version of Windows 10, I'm restricted in how I can prevent this update. I seem to be able to snooze it and hopefully I can do this an unlimited number of times (but knowing Microsoft this may not be the case).
Tim

--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/CAJ6OYomyMcO3YRf%3DnshpEZj9N-cN6qcG5PD5vzg4r5VosGi81Q%40mail.gmail.com.

[Kent Rasmussen]

No. You can always change OS, and for free. :-) -Kent

On 05/05/2017 03:50 AM, Tim Gaved wrote:
> Is the only solution to wait for Microsoft to fix to their bug?

--
Kent Rasmussen
SIL Eastern Congo Group Linguistics Consultant / Conseiller en Linguistique de SIL au Congo de l'Est
Orthographies for eastern DRC / Orthographes pour la RDC de l'est
+1-541-357-7276

[KevinC99]

Do you have more information about what the bug is? Is it something that other programs would have problems with as well?

Kevin

[chas]

I was hit by this bug, too, but I'm afraid I've already reverted to the previous build of Windows 10, so I hope not to encounter the bug in the future.

I need to remember always to wait 3-6 months before updating to the latest and greatest Windows release!

At least Win10 had an easy way to revert to the previous build. 

-Charlie L.

[chas]

Is this a problem that could possibly affect other current SIL software? 

Thanks!

-Charlie L.

[Mike Maxwell]

On 5/12/2017 2:41 PM, chas wrote:
> Is this a problem that could possibly affect other current SIL software?

I think the real question is whether it affects anyone else's software,
and preferably some widely used software. If it does, then there's a
chance Microsoft will fix it. If it doesn't, the chances of them
spending the time to fix it just for FLEx are, IMO, slim; no matter how
many FLEx + Win10 users submit it and upvote each other, it's unlikely
to reach the threshold of importance from their viewpoint, simply
because there aren't that many FLEx users (and particularly FLEx users
who have migrated to Win10.

Besides, if FLEx is the _only_ software that triggers this error, then
one might logically assume it's a problem in FLEx, not in Windows.
Perhaps Win10 is performing more tests on library calls than Win7/8
were, and FLEx is making a bad library call. If the bug is reproducible
(which it apparently is), then someone on the development team should be
able to run a debugger and find out exactly what in the source code
triggers the crash.
--
Mike Maxwell
"My definition of an interesting universe is
one that has the capacity to study itself."
--Stephen Eastmond

[Paul Nelson]

The issue does happen with other software. Don't lose hope.

Paul

--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
--- You received this message because you are subscribed to the Google Groups "FLEx list" group.

To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+unsubscribe@googlegroups.com.

To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/59de439a-3a2f-9d29-0617-658d5d7c9b26%40umiacs.umd.edu.

[chas]

I ask because we use a handful of SIL apps besides FLEx on several different machines. Since I assume SIL devs re-use code as much as possible, I'm concerned that other SIL software might be susceptible.

[Hugh Paterson]

@Paul

I know what the symptom is but what is the cause? any comment there?

--

You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+unsubscribe@googlegroups.com.
To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/7f28b4f9-b66f-455c-9f7d-f776e3b2e2e9%40googlegroups.com.

[Hugh Paterson]

@Paul,

For those who are holding out on updating windows due to this bug issue with MS, are they now more vulnerable to WannaCry? - to which the solution seems to be "upgrade".

- Hugh

--
You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+unsubscribe@googlegroups.com.
To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/CAJ6OYomyMcO3YRf%3DnshpEZj9N-cN6qcG5PD5vzg4r5VosGi81Q%40mail.gmail.com.

[chas]

@Hugh,

"Some Windows 10 editions let you defer upgrades to your PC. When you defer upgrades, new Windows features won’t be downloaded or installed for several months. Deferring upgrades doesn’t affect security updates. Note that deferring upgrades will prevent you from getting the latest Windows features as soon as they’re available.”

https://support.microsoft.com/en-us/instantanswers/20a98a29-df85-b9e9-f04e-e7812bc903f6/defer-upgrades-in-windows-10

I believe when Microsoft says they “support” a given version or release of Windows, that means they continue issuing regular security updates for it. So you can safely revert to the Windows 10 Anniversary Update (version 1607) without risk of being hit by WannaCry. For that matter, you could even be running an older release of Windows, as long as there are regular security updates issued. 

[Disclaimer: My expertise on this subject goes back to Wednesday before last, when I got hit by this FLEx crash, but our IT guy said this was right.]

To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.

[Paul Nelson]

No. There is no greater vulnerability from waiting for the Creators
Edition of Windows.

The vulnerabilities in Windows was in the Windows Defender code which
was updated some time ago. The problem is when people don't run
Windows Defender, or are running on old systems that are no longer
patched.

Best regards,
Paul

>> email to flex-list+...@googlegroups.com.

>> To post to this group, send email to flex...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/flex-list/CAJ6OYomyMcO3YRf%3DnshpEZj9N-cN6qcG5PD5vzg4r5VosGi81Q%
>> 40mail.gmail.com

>> <https://groups.google.com/d/msgid/flex-list/CAJ6OYomyMcO3YRf%3DnshpEZj9N-cN6qcG5PD5vzg4r5VosGi81Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .

>> For more options, visit https://groups.google.com/d/optout.
>>
>

> --
> You are subscribed to the publicly accessible group "FLEx list".
> Only members can post but anyone can view messages on the website.
> To change your status, please write to flex_d...@sil.org.
> You can join this group by going to
> http://groups.google.com/group/flex-list.
> ---
> You received this message because you are subscribed to the Google Groups
> "FLEx list" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to flex-list+...@googlegroups.com.

> To post to this group, send email to flex...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/flex-list/CAB0NEmwHe-5VnD0dk6nh4Tip5jWKMA%2BBy5GmSg3YxEr2gSCaVQ%40mail.gmail.com.

[Mike Maxwell]

On 5/21/2017 12:25 AM, Paul Nelson wrote:
> No. There is no greater vulnerability from waiting for the Creators
> Edition of Windows.
>
> The vulnerabilities in Windows was in the Windows Defender code which
> was updated some time ago. The problem is when people don't run
> Windows Defender, or are running on old systems that are no longer
> patched.

Actually, while Windows Defender didn't detect WannaCry, the
vulnerability was in the underlying OS, not in WD. And Microsoft did
patch the vulnerability back in March, for Win7, Win8.1, and Win10. A
WinXP and Win8(.0) patch was later released. See details here:

https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-wannacrypt-attacks/
Windows Vista has not, afaik, been patched, but hopefully no one is
running that. (Nor for that matter should you be running XP.)

Bottom line: If your system is patched, you'll be safe even if you're
running some antivirus other than Windows Defender. (I suspect, but
don't know, that other antivirus products now block WannaCry as well.)

Mike Maxwell
University of Maryland

[chas]

A co-worker wants to know if this Windows Creators' Update crash affects FLEx  8.2.8.42510 from May 20, 2016. Does anyone know? I've read here of crashes on 8.2.9, so I'm guessing 8.2.8 is also affected, but he'd like to know. I told him I thought he shouldn't risk it.

Thanks.

-Charlie L.

On Tuesday, May 2, 2017 at 2:13:47 PM UTC+1, Paul Nelson wrote:

[Ken Zook]

The Windows bug probably affects every version of Flex, although I haven’t tested it earlier than FW8.2.

 

Ken

 

From: flex...@googlegroups.com [mailto:flex...@googlegroups.com] On Behalf Of chas
Sent: Monday, May 22, 2017 2:15 AM
To: FLEx list <flex...@googlegroups.com>
Subject: [FLEx] Re: Windows 10 update 1703 crashes in FieldWorks

 

A co-worker wants to know if this Windows Creators' Update crash affects FLEx  8.2.8.42510 from May 20, 2016. Does anyone know? I've read here of crashes on 8.2.9, so I'm guessing 8.2.8 is also affected, but he'd like to know. I told him I thought he shouldn't risk it.

--

You are subscribed to the publicly accessible group "FLEx list".
Only members can post but anyone can view messages on the website.
To change your status, please write to flex_d...@sil.org.
You can join this group by going to http://groups.google.com/group/flex-list.
---
You received this message because you are subscribed to the Google Groups "FLEx list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+...@googlegroups.com.
To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/e17fff3c-966c-482b-ba9b-081b081a821f%40googlegroups.com.

[chas]

Thank you, Ken. I relayed this info to my co-worker.

-Charlie L.

[chas]

Is there any indication this problem is related to the later version of .NET (4.7 instead of 4.6) that gets installed with Windows 10 Creators' Update? 

Thanks.

[Paul Nelson]

This crash began with Creators Update. Other apps are reporting similar issues. If you use Paratext, you should receive a mail in the next day or two with directions to uninstall as they are suffering performance issues after Creators Update is installed. :-(

To unsubscribe from this group and stop receiving emails from it, send an email to flex-list+unsubscribe@googlegroups.com.

To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/4de97997-5b52-4f15-8971-8e7681df9a7d%40googlegroups.com.

[chas]

FWIW, the FLEx crashing problem is still there with Windows 10 Pro Insider Preview build 16193.1001 (still version 1703). I wanted to try build 16199, but I couldn't successfully install it.

-Charlie L.

[Kevin Cline]

I installed 16199 last night and it's still there.

You received this message because you are subscribed to a topic in the Google Groups "FLEx list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/flex-list/fdNOnkUXn64/unsubscribe.
To unsubscribe from this group and all its topics, send an email to flex-list+...@googlegroups.com.

To post to this group, send email to flex...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/e3554862-60d2-4181-9d3d-c29e1d3d5721%40googlegroups.com.

[Stevan Vanderwerf]

I installed Windows 10 Fall Creator's Update preview (build 16215) and noticed the same crashes in FLEx.

https://blogs.windows.com/windowsexperience/2017/06/08/announcing-windows-10-insider-preview-build-16215-pc-build-15222-mobile/

Stevan   

To view this discussion on the web visit https://groups.google.com/d/msgid/flex-list/CAC6wTJKC-iagmVcHt1u%3DjiLXHkqhB3Xt-GWoYnXo%3Do%3D3YJqWtg%40mail.gmail.com.

[chas]

Thank you, Stevan. That saves me the trouble of trying build 16215. Maybe soon one of these previews will fix our problem. Does anyone out there own a lot of shares in Microsoft?

[Andreas_Joswig]

On 09.06.2017 14:11, chas wrote:
> Does anyone out there own a lot of shares in Microsoft?

Oooh, I wish I had. It would make me a rich man...
Andreas