Domino Designer Still Crashes After Windows 10 Creators Update

Current as of July 10, 2017.  I can reproduce a BSOD crash in Windows 10 while using Domino Designer.  This is with the v1703 update to Windows 10 that was installed during the last week of June.  Daniel Nashed reported that the crash had been addressed with the 1703 update, but it appears that the crash that was resolved was the one caused by customizations to the Notes client home page (ht to Howard Greenberg for the clarification).

To avoid the crash when using Domino Designer, DO NOT do this:

  • add a Computed Field control to your XPage/Custom Control
  • in Design mode, select the Value tab
  • change the value to be JavaScript and click in the edit panel
  • boom!

You can get around this by manually coding the SSJS using the Source panel instead.

I’m using Domino Designer 9.0.1 FP7 SHF143 and Windows 10 v1703 (in a VM on a Mac Book Pro)



I am an IT professional with over 20 years of experience. For much of that time I have worked with IBM Lotus Notes and Domino, helping organizations take full advantage of the tool for building workflow collaboration solutions. I have ITIL certification and a background in project management as well. Recently I have invested in how mobile devices may be used to extend business applications outside the office, and have also been learning how to add social components to traditional business applications. Away from work, I have three daughters and recently celebrated my 20th wedding anniversary with my wife in Hawaii. I coach hockey, cycle, and love growing garlic and then finding new ways to use it. I added a section of herbs to my garden last year and was very happy with the result. I ride my bike each year with my wife in the Ride to Conquer Cancer to raise money for research in childhood cancers, particularly brain tumours. Our youngest daughter lost her battle with a brain tumour in 2008 and through this ride we hope to help find a way to prevent other families from experiencing what we went through and continue to live with. If I have any spare time, I like to travel, so you may see the odd photo from our family adventures here too.

Posted in Uncategorized
8 comments on “Domino Designer Still Crashes After Windows 10 Creators Update
  1. 2017, a software not running thru core drivers giving BSOD
    I must say it feels like a flash back to windows 3.11

    I have received some BSOD on my Windows 10 machine but never connected them to Notes.
    Will try the above to check this on my machine also 😉

  2. newbs56 says:

    When I first read about this I told my team: “Go to the Windows Update Setting – Advanced Settings and select :’Defer Feature Updates'”. Got no Creators Update installed so far.

    • gacres99 says:

      I’ve confirmed this morning, with the help of Martin’s team at IBM, that Daniel’s post was in fact correct, and that the latest latest update is good. You have to do the install manually though. Blog post later tonight when I have time on the details.

  3. […] I thought I had been thorough prior to writing my blog post yesterday about Domino Designer crashing Windows 10 after the Creators update, I’d missed the fine print.  This is to clarify what I missed and what you need to do as […]

  4. JeffB says:

    I’m in deep shit here. I first had the BSOD, then I updated, finally to KB4025342 and now there’s no crash but I cannot use the Domino Designer. An XAgent cannot be updated, not even on the Source tab, because saving the XPage doesn’t work. Usually, no events are shown on the Events tab, not on the view tag, not on an image tag.
    I wonder, do they still work for you?

    • gacres99 says:

      Wow! I ended up enduring the KB4025342 update this afternoon right at a time when I really didn’t need it. But, no issues using Domino Designer. I’ve mostly been doing old school Domino stuff today, but have been writing Java, and just played with a custom control as you describe. All good for me. Send a tweet to @TweeterDonnelly with the details. I will post to the Slack chat too and see what others have seen.

  5. JeffB says:

    I guess I did something wrong: I had MalwareBytes running, and it refused to remove notes2.exe in some sub-sub-folder. I corrected this, by exiting MWB and reinstalling Notes+FP8, and it works a lot better. One serious problem left: the JS Editor refuses to work on computed values.

  6. JeffB says:

    Corrupted workspace. I renamed it, then restarted Notes, and all seems okay now.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: