Styles in word 2016 not working properly

Anonymous
2015-12-28T04:19:27+00:00

Dear All,

I need help from you.

I cannot use Styles in Word 2016 properly, the problem is:

I want to use "Body Text", "Heading", "List Bullet", "List Number". When I click on "Body Text" but it jump to "TOC", it is not exactly "Body Text".

When I click on "Heading 1" it jump to "Heading 2" and next click jump to "Heading 3" and so on.

In previous version I always use these Styles but not faced these Problem.

After I change to this version I facing with this problem.

I use Microsoft Office Home and Business 2016.

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2016-01-14T19:53:46+00:00

Hi everyone!

The Office 2016 December update introduced an issue where the wrong style would get applied if you tried to select a style in the Styles pane.

That issue has been fixed in update 6366.2056, which is rolling out now to Office 365 consumer/small business subscribers. If you don't see the update yet, follow these steps:

  1. Open any Office application and choose File > Account. (If you're using Outlook, choose File > Office Account.)
  2. Under Product Information, choose Update Options > Update Now.

If you're still experiencing issues in 6366.2056, please let us know (best to start a new thread).

Thanks for your patience.

Was this answer helpful?

0 comments No comments

103 additional answers

Sort by: Newest
  1. Doug Robbins - MVP - Office Apps and Services 323.6K Reputation points MVP Volunteer Moderator
    2016-01-07T23:16:25+00:00

    Make your suggestion at

    http://word.uservoice.com/

    In the meantime, make use of the Styler Add-in referred to in my earlier responses in this thread.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-07T23:12:27+00:00

    I believe that under these circumstances, MICROSOFT should allow us to revert back to Office 365 (2013) until they fix the problem, because it's frustrating and time-consuming without making progress.

    Additionally, MSFT should not show the upgrade to 2016 bar until the problem is fixed. By having the bar, users will run headlong into the issue, when an alert would warn them. Instead of the "upgrade to Word 2016" bar, have a "Don't upgrade to Word 2016 until further notice, we're fixing a bug". Thanks for your patience with us.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-01-07T19:25:41+00:00

    Sounds interesting William,

    I've talk to MS Techs twice (whatta pain) and there is a MS MVP that is responding to our posts ..........besides the Styles issues there is also a Word saving issue as well ........sometimes when working with an existing old document and opening in Word 2016, once it asks to convert to compatibility mode and updates it becomes a Read-Only doc and you have to rename and save it............MS also is aware of this issue.

    Some people have uninstalled Word 2016 and backtracked to Word 2013 and that works, but what a pain .....MS should jump on this fix as it is costing time for thousands of users working with the workaround. As a writer and Proposal Manager my time is doubled having this issue and working with a time consuming workaround.

    Let us know how the hardware acceleration works out. I also updated the NVidia drivers but that didn't help either. It's a Windows 10/Word 2016 bug.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-01-07T18:57:20+00:00

    Okay, I'm seeing a common thread. One other person had an NVidia card as well. Mine's only a GeForce 465 but both from NVidia. I talked to NVidia and they gave me a back-version driver.  This did not fix the problem but I'm now trying another fix (suggested by an MVP)--Disable Hardware Accelleration. This looks promising.

    Was this answer helpful?

    0 comments No comments