Revit 2022 hangs on "color fills calculating" background process

[JiriTomek4485]

Hello,

we just bought 6 new workstations (Intel Core i9-12900K, 32GB RAM, 500GB M2 SSD) running Windows 11 and running Revit 2022 with latest Hotfix 2 on them. When we open a specific Revit model which contains the room color fills the Revit starts background task "color fills calculating" and blocks any operations with the model such as "save" or even "close" until the task is finished. The task runs for several minutes and then fails so it makes the work with the model practically impossible. I'm attaching the screenshot for the reference:

The exact same model opened in the exact same version of Revit 2022 but running on Windows 10 works just fine. We have tried it on all 6 new PCs and it fails on all of them. We have 2 different Graphic card models in them - AMD FirePro and NVidia Quadro, both with latest drivers and it fails on both, so it's not a graphic card or driver issue. The older Windows 10 workstations are very similar, they have just older CPU model but same graphic cards, same amount of RAM etc. so it has to be something with Windows 11.

Did anyone encounter similar issue? Anything to try?

[ennujozlagam]

https://knowledge.autodesk.com/support/revit/troubleshooting/caas/sfdcarticles/sfdcarticles/SQLDUMPE...

[JiriTomek4485]

Thanks, but my issue is not related to SQL server and console window opening.

[RSomppi]

Since Revit 2022 came out before Windows 11 and 2023 is right around the corner, I would wait until Revit 2024 comes out to run Revit on Windows 11.

[ToanDN]

[JiriTomek4485]

Unfortunately that's not an option, we can't let 6 people just sit and do nothing. 🙂

[ArianaPeppers]

I had this issue too. I needed to save, so I went to the task manager and when I create a dump file it causes the background processor to have an "error" which allowed me to cut it off and save my project. 

Hope that helps!

[JiriTomek4485]

After some back and forth with Autodesk we figured out that the cause is the wrong (too big) disk sector size in Windows. 

I ran fsutil fsinfo sectorinfo C: and the output was following:

LogicalBytesPerSector :                                 512
PhysicalBytesPerSectorForAtomicity :                    32768
PhysicalBytesPerSectorForPerformance :                  32768
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096
Device Alignment :                                      Aligned (0x000)
Partition alignment on device :                         Aligned (0x000)
No Seek Penalty
Trim Supported
Not DAX capable
Not Thinly-Provisioned

I applied registry change described at https://learn.microsoft.com/en-us/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size to set PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance to 4096, reinstalled MS SQL 2014 and it fixed the issue.