Can't add pictures as new bullets in MS Word. Bad Request-Request too long

Anonymous
2024-01-27T20:46:13+00:00

When I try to add pictures to define a new bullet it shows "Bad Request - Request too long / HTTP Error 400. The size of the request headers is too long."

It doesn't matter if I do it from the bullet button in the ribbon, or defining a new list style. I don't have that problem when adding a regular picture or even icons.

I've tried:

  1. Deleting the ListGal.dat file as suggested in another post
  2. Replacing the Normal.dot global template file as suggested in the same post
  3. Clearing the officefilecache folder
  4. Going offline (the same window appears but blank)
  5. Repairing through the Windows repair option

I'm on Windows 11, using the desktop app. I was using MS Word version 2312 (Build 17126.20132), and just before writing this post I checked for updates again (I had already tried a few days back with no success) and it actually updated to Version 2401 (Build 17231.20084). I opened Word the Bad Request didn't appear. I opened a new file and tried again and the message came up again!

I hope I gave enough information!

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

47 answers

Sort by: Newest
  1. Anonymous
    2024-04-08T03:27:11+00:00

    Vâng, đó là sự thật, đó chính xác là cách khắc phục lỗi đó.

    Guys you must to change the MS account to fix that.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-04-04T14:28:08+00:00

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-04-02T11:52:22+00:00

    This worked for me! Thanks MauriceSuter

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-03-30T06:20:50+00:00

    Classic large corporation, raise the price of subscription, get worse at delivering the service. What's the ETA on getting it fixed?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-03-26T19:34:26+00:00

    Same problem as everyone else here.

    It's been at least a month or two since the problem was reported.

    I thought the whole idea of this new subscription model is that the software is under constant review, with regular updates and bug-fixes.

    Can someone @Microsoft confirm that they're looking into this or - even better - give us a rough idea, how long we'll have to wait until the product we're paying for is working properly again?

    P.S.: I'd like to add that the problem is not persistent. It just keeps popping up, then solves itself again.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments