Community
It could still be an upgrade even if delivered new with W11...
It does not necessarily have to be the cause but the colleagues here from IT here confirmed that they have seen the SQLDumper black window on 3 machines after upgrade from Windows 10 to 11. A fresh install of W11 iso fixed it. All 3 machines did not even have Revit on. The window was triggered by another software.
It might be worth checking whether the OS was upgraded... Run Regedit and check if there is an Upgrade and Source OS Keys under the following path...
HKEY_LOCAL_MACHINE\SYSTEM\Setup
Otherwise, good luck with Autodesk and finding a solution. And if you do find something do share it
I called the pc-dealer and asked, he told me that there is an windows 11 installed with no upgrades from windows 10 or so.
An experienced REVIT-user told me, that REVIT isn´t yet coordinated with windows 11 and that I have to wait for another patch.
Now I wait for Autodesk´s response.
Thank you once again for your help!
I will keep you updated!
Dear All,
The following solution is working for me. I have worked it out with the help of the Autodesk Support Team with the Revit Developer team involved. It solved the SQLDUMPER.EXE problem, AND the colour fill calculation issue. (By colour fill issue I’m referring to the automatic room colouring based on rules, like Room name)
As someone sad before me the problem is in the communication between Revit and Windows. Revit is assuming you have either 512 or 4096 byte sized sector sizes to work with. Put the following string into PowerShell as an administrator (otherwise it will not work):
fsutil fsinfo sectorinfo C:
For me it was looked like this before the fix:
You have to pay attention to the Physical bytes (Not the LogicalBytesPerSector). You will have to change that to make Revit work properly.
Here is what you have to do:
- Reinstall SQLLocalDB from the Revit kit (SqlLocalDB.msi is in the Delivery\rvt\3rdParty\x64\Sql folder). Or use any other source, but this was worked for me.
- Than we have to force Windows to think it is working with 4096 (or 4095) bytes per sector. Folow one of the solutions in the link below. In this article you will see SQL server 2016, 2017, 2019, but the solution here is works with 2014! That was one of the reasons it was taken me 5 weeks to find this:
docs.microsoft.com/en-us/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size
Registry Editor:
- Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device.
- On the Edit menu, point to New, and then select Multi-String value. Name it ForcedPhysicalSectorSizeInBytes.
- Modify the new value, type in * 4095. Click OK and close the Registry editor.
- After you follow threw one of the suggested solutions (I used the one under “Registry editor” I copied it above so you do not have to look for it) you have to restart the system.
- If you did everything right, Revit should work just fine from now on, and physical bytes per sector should have changed to the desired number. Check it with the same method i mentioned in the first part.
Summary:
This solution fixed all versions of Revit under Win 11 for me.
I hope this works for you too.
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
