Classic / Legacy FileNew dialog crashes Word. Release 1903

Apparently release 1903 for Word 2019/365 removed access to the classic FileNew dialog for some users.

  1. The command i in the Keyboard Shortcut customization dialog will crash Word.
  2. The command in the QAT customization dialog will crash Word.
  3. The vba command
    application.Dialogs(wdDialogFileNew).Show
    will crash Word.

UserVoice request on this is here. Please vote and comment.
https://word.uservoice.com/forums/30...oved-from-1903


File New Variations in the Versions of Word

Reports of this problem in these threads:

This is not affecting everyone. See responses by MVPs Doug Robbins and Stefan Blom, neither of whom are seeing the problem.

Update 4/11:

Just tested on a separate computer using same Office 365 subscription and same build/release.

The vba command did not crash Word.

 

Discussion Info


Last updated July 23, 2019 Views 349 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I just checked a 1903 version of Word 2016. It does not show this problem. It was updated today before I checked this. I cannot say for sure that it applies to Word 2019 since I am using 365.
Please mark helpful or answered as appropriate to help other users.

Charles Kenyon
Attorney at Law
Madison, Wisconsin
wordfaq[at]addbalance[dot]com

http://addbalance.com/usersguide/styles.htm
No problem with Microsoft Office Professional Plus 2019 with Version 1903 (Build 11425.20202) or after updating just now to Version 1903 (Build 11425.20204).
Hope this helps,
Doug Robbins - MVP Office Apps & Services (Word)
dougrobbinsmvp@gmail.com
Screen shots by Snagit from www.techsmith.com

No problem with Microsoft Office Professional Plus 2019 with Version 1903 (Build 11425.20202) or after updating just now to Version 1903 (Build 11425.20204).

Hm. Must just be 365.

There were two posts about this in the last two days.

I just tried the vba in Safe mode and did not have the problem with the vba command.

Please mark helpful or answered as appropriate to help other users.

Charles Kenyon
Attorney at Law
Madison, Wisconsin
wordfaq[at]addbalance[dot]com

http://addbalance.com/usersguide/styles.htm

Then tried with new normal.dotm and it crashed.

Then tried with no Add-ins and new normal.dotm and it crashed.

Trying quick repair now although that shouldn't do anything.

Did nothing. Will try online repair.

Please mark helpful or answered as appropriate to help other users.

Charles Kenyon
Attorney at Law
Madison, Wisconsin
wordfaq[at]addbalance[dot]com

http://addbalance.com/usersguide/styles.htm

Jay Freedman reported in Eileen's lounge:

In the Office 365 ProPlus version of Word 2016 (v. 1903 Build 11425.20204), the VBA statement does crash Word, even in safe mode.

Please mark helpful or answered as appropriate to help other users.

Charles Kenyon
Attorney at Law
Madison, Wisconsin
wordfaq[at]addbalance[dot]com

http://addbalance.com/usersguide/styles.htm
Version 1903, (Build 11425.20204) of Office 365 ProPlus would NOT show a year (2016 nor 2019).  The splash screen that appears when it is started shows 
Hope this helps,
Doug Robbins - MVP Office Apps & Services (Word)
dougrobbinsmvp@gmail.com
Screen shots by Snagit from www.techsmith.com
In the post that Charles referenced, I said it was Word 2016 only to indicate that it isn't 2019. I don't care what the splash screen says, it's still the same old pile of bugs. <g>
_____________________________
https://jay-freedman.info

But was it Office 365 ProPlus version 1903 (Build 11425.20204)

 Stefan Blom confirms my observation that there is no issue with the legacy File>New dialog (New document or template).

Hope this helps,
Doug Robbins - MVP Office Apps & Services (Word)
dougrobbinsmvp@gmail.com
Screen shots by Snagit from www.techsmith.com

But was it Office 365 ProPlus version 1903 (Build 11425.20204)

***

 Stefan Blom confirms my observation that there is no issue with the legacy File>New dialog (New document or template).

Doug, Some users are seeing these crashes. I first saw them and saw reports here with release 1903. I observed the problem with build 11425.20200 and still with 11425.20204.

Most users will not see a problem because most users do not attempt to use the dialog.

That you and Stefan are not seeing the problem is a good sign, but it does not mean that there is no problem. I am hoping that this is a bug rather than a deliberate change.

I tested a separate installation of 2016 perpetual HUP license with release 1903 and there was not a problem.

Please mark helpful or answered as appropriate to help other users.

Charles Kenyon
Attorney at Law
Madison, Wisconsin
wordfaq[at]addbalance[dot]com

http://addbalance.com/usersguide/styles.htm

update:

Just tested on a separate computer using same Office 365 subscription and same build/release.

The vba command did not crash Word.

Back to original system, the vba command crashes Word except when Word is started in safe mode.

So, next question is when Word is started:

  1. After an online repair
  2. Using the /a switch to disable Add-Ins
  3. With Normal.dotm renamed
  4. and the vba command crashes Word...

What local factors needs to be checked to see what is causing this?

Please mark helpful or answered as appropriate to help other users.

Charles Kenyon
Attorney at Law
Madison, Wisconsin
wordfaq[at]addbalance[dot]com

http://addbalance.com/usersguide/styles.htm

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.