RockPack III "MSSTDFMT.DLL" error

[Guest Molly]

A user has reported a DLL error running the Safety Factor Calculations in RockPack III on a Windows 10 64-bit computer:

 

Class not registered.
You need the following file to be installed on your machine.
MSSTDFMT.DLL.

 

This is a DLL which is apparently not installed with newer versions of Windows, and it is required by RockPack III.

 

Solution:

1. Find this DLL:

• First search your own computer for MSSTDFMT.DLL.
• If you cannot find it locally, search your company network computers for known safe copies of this DLL (probably from installations of older software).
• If you cannot find it on your network, you can also do a search on the microsoft.com site.
• We do not recommend downloading DLLs from "DLL Download" websites. 

 

2. Once you locate a copy of the MSSTDFMT.DLL file, copy it to one of these system folders:

If you have a 32-bit computer: c:\windows\system32\
If you have a 64-bit computer: c:\windows\syswow64\

 

3. Register the DLL

• In the Search box on the Windows 10 taskbar, type in:   cmd
• You should see the "Command Prompt, Desktop App" displayed in the results.
• Right-click on this item and select Run As Administrator.
• Click Yes if prompted to confirm it's ok for this program to make changes to your system.
• At the command prompt, type one of the following and press the Enter key:
  32-bit:   regsvr32 c:\windows\system32\msstdfmt.dll
  64-bit:   regsvr32 c:\windows\syswow64\msstdfmt.dll
  Note that there is a space between "regsvr32" and "c:\windows\..."
• If the registration is successful you'll be notified as such.
  Here is a quick video of how to access the command prompt.

 

4. Start RockPack III and see if the tools in the Safety Factors Calculations menu now launch.

 

Contact our support group if you need additional information.

 

Molly 

RockWare Inc.

 

 

[Alison]

We recommend that users take a look at this new forum posting before following the instructions above:  

 

It appears that the installation of a patch posted on the RockWare website (related to a known bug in RockPack) may also fix this issue.