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

47 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-02-02T01:06:51+00:00

    I am having the same issue. How do we fix this problem?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-01-31T18:31:57+00:00

    Same problem here....having to import custom image bullets as pictures one at a time....annoying.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-01-30T01:56:27+00:00

    +1 I have the same issue and tested exactly the sam

    Well, yesterday it was working. Today it went to the "bad request" message again. I really thought it was fixed, I don't know what's going on.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-01-29T20:31:15+00:00

    +1 I have the same issue and tested exactly the sam

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Suzanne S Barnhill 279.4K Reputation points MVP Volunteer Moderator
    2024-01-28T23:07:21+00:00

    Great! Thanks for reporting back!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments