For many weeks, I've been experiencing excessive Office Pro 2016 program initialization/load problems after incorporating the Windows 10 Fall Creator Update (Version 1709). It was taking such Office programs like Word 30 - 60 seconds to load (initialize). I could verify that the Windows 10 Pro update (Version 1709) was the problem since I could easily reimage my disk to Version 1703 and the excessive initialization problems no longer existed (I also had to have gone back to whatever was the Malwarebytes Premium version that was on my computer when I did the backup). I spent many days trying every performance issue suggestion including reloading (not clean ISO) Windows 10 Pro 64-bit and Office 2016 Pro. Even though my environment was exactly the same prior to the Fall Creators Update (1709), I put off looking at my security programs. I turned off Norton Security - no change, still 30 second initialization times. Quit Malwarebyes (Premium), up comes do you want Malwarebytes to change your system --> YES, start Word 2016, my god I am back to 5 second initializations. It must be that Malwarebytes Premium is the problem!! Restart my machine to see if Malwarebytes was uninstalled when I checked the Quit Malwarebytes option (right click on Malwarebytes system tray icon). No, as expected Malwarebytes is back in the fold after the restart (I didn't uninstall since I wasn't asked to uninstall Malwarebytes Premium). But guess what, the Office program initializations are back to 5 - 10 second which was the Office Pro 2016 issue prior to the Version 1709 update of Windows 10 Pro. Somehow stopping (Quit in Malwarebytes terminology) and restarting Malwarebytes (by doing a computer restart) seems to have fixed my 30 to 60 second Office program initialization issues. No idea why this fixed the Office 2016 program load/initialization problems. Checked this solution on my two other machines that had the same problem (same environment) and the Office 2016 programs are back to their pre-1709 update initialization times. Never any problems with anything other than Office 2016 program start times. I don't understand why Malwarebytes was the problem but take this story for whatever it is worth. I will ask Mr. Gates for forgiveness on this second Sunday in Lent.