Windows 10 updated, Office 365

I have spent the last half-hour attempting to restore my Normal.dotm template after a client's obligatory OneDrive connection and working through their SharePoint brought all sorts of unwanted para styles into it. I have replaced the Normal.dotm in my user accounts as well as the administrator account, customizing the styles and applying on to the blank paragraph with which Word opens. However, opening Word in my user accounts continues to open a document based on a template that is not showing the latest changes. How do I track it down?



The one I know about resides in User/AppData/Roaming/Microsoft/Templates.

I am opening Word from the desktop Windows menu.

Verify that you are looking in the correct templates folder. You want the one which is defined as the User Templates folder in the File Locations dialog box (File > Options > Advanced > File Locations).

Even after you have verified the User Templates folder, ensure that it doesn't contain any "backup" versions called Normal1, PreNormal or NormalPre, as those may be used if the template called Normal.dotm is missing.

__________________
Stefan Blom
Microsoft Word MVP

Microsoft 365 apps for business
Windows 11 Professional

You can use VBA to show where the Normal.dotm is actually located. For instance, paste this line into the VBA Immediate Window and press enter to see the full path to your currently active Normal template.

__________________
Andrew Lockton
Chrysalis Design, Melbourne Australia

Resolved. Thanks. Why, I don't know, though. I opened the Normal.dotm at a location I had checked twice yesterday, before and after rebooting teh machine, and this time it showed the defective version, easily corrected, and now what comes up from Windows menu and taskbar shortcut is fine.

(I say "at a location," because, due to a computer refresh last year at a service place, I ended up, as I once did before, with two apparent users in place of one. I have left them, because I don't want to lose any possible info by deleting one (yes, I have backups, but who want;s to check every file?) and it's reportedly a tricky Windows issue.
Everything works fine, mostly; this little glitch was a rare gremlin.)

Thanks to you both!