Office 2016 apps prompt save as dialog twice, first through the backstage view and then the normal save as dialog box

The two above links are very similar to the problem my client is experiencing.  There is a workaround in the second link which says to disable the backstage view.  However many people grow accustomed to this view and I think it is a bug with Office and Windows.

The other thing is Microsoft standard fix for everything instead of fixing the actual bug is to do an online repair install.

Open up Word 2016, create a new document, type in some words, save as, in the backstage view, click on a folder, any folder, and then save.  Eventually the normal save as dialog box pops up again asking you to save the document.  Sometimes the document is already there and if you hit save it’ll ask if you want to overwrite the existing document that was saved via the backstage view a few seconds prior or the document is not there at all.


I am actually having the same problem and I was able to recreate it on my own workstation.

Steps to reproduce the problem:

  1. Open up Microsoft Word
  2. Click on Blank Document
  3. Type anything into document
  4. File > Save As
  5. Choose someplace within Recent
  6. I choose a folder on OneDrive for Business by double-clicking on the folder
  7. Click Save
  8. Wait for it to kick you back to the document
  9. Another Save As dialog box will appear

Windows 10 long file paths and file names cause Windows Explorer to crash

Ever since Microsoft released its anniversary update to Windows 10, they introduced a new feature which enables file names and paths longer than 260 characters.  However, in doing this, they introduced a bug that is causing a lot of problems.

If you had Windows 10 and are connected to a file server or even a network attached storage device and you had file paths that were longer than 260 characters, for the most part Windows would not complain.  It would allow you to modify, save, create etc. files with no problems.

After the Windows 10 anniversary update which included the new feature to allow file paths and names longer than 260 characters this broke everything.  You see, you can able this feature through group policy and the only things that support or will allow you to use this new feature is a very limited group of applications.  The application has to specifically be told to use this feature so everyone including Microsoft has to update their programs to utilize this feature.  Windows Explorer in its current form does not support file paths and names longer than 260 characters.  Whatever they did to include the new code which allows file paths and names longer than 260 characters is what is causing this bug to happen.

Symptoms of the bug is when you view a file or folder within Windows Explorer that has a file path longer than 260 characters Windows Explorer will close.  Your desktop may also flash black momentarily and then come back with just your desktop showing.  Another symptom of this bug is when you have a folder or file that is longer than 260 characters that is in your quick access area which is the default folder/area that Windows Explorer opens up to you will see a blinking Windows Explorer window non stop.  I’ve also hard of people being unable to drag Windows Explorer windows across their desktop.

There are two workarounds for this as it stands but they’re simply that, workarounds, these are not permanent fixes because it gimps Windows Explorer.

The first is to go to View, Options, Change Folder and Search Options, click on the View tab, CHECK off Always show icons, never thumbnails.

The second is to change the way Windows Explorer opens up to quick access: Again View, Options, Change Folder and Search Options, on the General tab at the very top it says “Open File Explorer to and there is a drop down box with “Quick access” already select.  Change it to This PC. and hit apply and then OK.

You can follow this thread: where there are multiple people confirming this bug.

Quota Underflow blue screen of death BSOD on Windows 7 64-bit

Looks like came across something new for Windows 7 64-bit.  Blue screen while using random programs like Chrome, FireFox, Internet Explorer, and the Memory.dmp file is indicating a quota underflow issue.  It does not pin point an exact file.  I used the Windows Debugger tool with the Windows 7 64-bit symbols and still no dice.