Fix: AccelerometerSt.exe Error on Windows 10

Described above is the error message that countless Windows 10 users are seeing every single time they boot their computers up and log into them ever since they downloaded and installed the Windows 10 Creators Update. The Windows 10 Creators Update, like many major Windows updates before it, has been found to be infested with all kinds of different bugs and problems, and while this error message is more of a nuisance than an actual problem, it is still quite annoying.

Users affected by this problem see this error message every single time they log in to their computers after booting it up, and it only goes away once the dismiss it. This problem has a wide array of different causes – from the VCRUNTIME140.dll file simply being corrupt or missing or an issue with a program known as HP 3D DriveGuard to the affected computer not having the latest Visual C++ redistributable package for Visual Studio 2015 or the redistributable package being corrupt. That being the case, there are also quite a few different possible solutions to this problem.

The following are the most effective solutions that you can use to try and fix this issue on your own:

Solution 1: Run an SFC scan

The SFC scan utility comes pre-installed on all versions of the Windows Operating System and is specifically designed to search computers for damaged or corrupt system files and either repair any that it finds or replace them with cached versions. If you’re seeing the error message described above every time your computer boots up, running an SFC scan is an exceptionally good place to start if you want to get rid of the error message. To run an SFC scan on a computer running on the Creators Update, you need to:

1. Press the Windows Logo key + X or right-click on the Start menu button to open the WinX Menu, and click on Windows PowerShell (Admin).
2. Type the following command into the elevated instance of Windows PowerShell and press Enter:

sfc /scannow

3. Wait for the command to be executed and for SFC to work its magic. SFC will inform you of its findings once the scan is complete.

Solution 2: Un-register and then re-register VCRUNTIME140.dll

If your computer has the VCRUNTIME140.dll file but is still displaying the error message described above, the Creators Update may have messed with its registration and it probably just needs to be registered with your Operating System. In order to see whether or not VCRUNTIME140.dll exists on your computer, you need to:

1. Press the Windows Logo key + E to launch the File Explorer.
2. Navigate to the following directory:

X:\Windows\System32

Note: In the directory above, replace X with the drive letter corresponding to the partition of your computer’s hard drive that Windows is installed on.

3. Sift through the contents of the directory and see if you can locate the dll file.

If the VCRUNTIME140.dll file does not exist on your computer, simply try out a different solution. If the VCRUNTIME140.dll file does exist on your computer, you need to un-register and then re-register it. To do so, simply:

1. Press the Windows Logo key + R to open a Run
2. Type the following into the Run dialog and press Enter:

Regsvr32 /u c:\Windows\System32\VCRUNTIME140.dll

3. Press the Windows Logo key + R to open a Run
4. Type the following into the Run dialog and press Enter:

Regsvr32 c:\Windows\System32\VCRUNTIME140.dll

Once done, restart your computer and check to see whether or not the error message rears its ugly head when the computer boots up and you sign in to it.

Solution 3: Uninstall HP 3D DriveGuard (For HP users only)

If you’re experiencing this problem on an HP computer, there is a good chance that the cause of your sorrows is a stock HP application named HP 3D DriveGuard. HP 3D DriveGuard is actually a hard drive protection application designed primarily for laptops, but for some reason it is prone to going rogue and giving birth to this problem once the Creators Update has been downloaded and installed. To uninstall HP 3D DriveGuard, you need to:

1. Open the Start Menu.
2. Click on Settings.
3. Click on System.
4. In the left pane of the window, click on Apps & features.
5. In the right pane of the window, locate the listing for HP 3D DriveGuard, click on it to select it, and click on Uninstall.
6. Follow the uninstallation wizard all the way through to the end until HP 3D DriveGuard has been successfully uninstalled.
7. Once HP 3D DriveGuard has been uninstalled, restart your computer and check to see whether or not the problem has been fixed when it boots up.

HP 3D DriveGuard is a hard drive protection application after all, and it actually does a pretty good job. So if you uninstall it to fix this problem but still want it on your computer, click here to download a version of HP 3D DriveGuard that is compatible with the Creators Update and doesn’t cause any unwanted issues and install it on your computer.

Solution 4: Download and install Microsoft Visual C++ Redistributable Package Update 3 for Visual Studio 2015

1. Go here, select your preferred language from the dropdown menu, click on Download, check the checkbox beside x86.exe (if your computer is running on a 32-bit version of Windows 10) or the checkbox beside vc_redist.x64.exe (if your computer is running on a 64-bit version of Windows 10), click on Next, and your download will start automatically.
2. Wait for the installer for the Redistributable Package to be downloaded.
3. Once the installer has been downloaded, navigate to where it was saved to, locate it and double-click on it to launch it.
4. Go through the installation wizard all the way through to the end, at which point Microsoft Visual C++ Redistributable Package Update 3 for Visual Studio 2015 will have been successfully installed on your computer.
5. As soon as Microsoft Visual C++ Redistributable Package Update 3 for Visual Studio 2015 has been installed, restart your computer and check to see if the issue still persists when it starts up.

Solution 5: Repair the Microsoft Visual C++ Redistributable installed on your computer

1. Open the Start Menu.
2. Click on Settings.
3. Click on System.
4. In the left pane of the window, click on Apps & features.
5. In the right pane of the window, locate the listing for Microsoft Visual C++ 2015 Redistributable, click on it to select it, and click on Uninstall.
6. When the uninstallation wizard launches, click on Repair instead of clicking on Uninstall.
7. Follow the repair wizard all the way through to the end to repair your computer’s installation of the Microsoft Visual C++ 2015 Redistributable.

Note: If you find that there is more than one listing for Microsoft Visual C++ 2015 Redistributable (there are usually only two), perform steps 5–7 for every single one of the listings.

8. Once the Microsoft Visual C++ 2015 Redistributable has been repaired, restart your computer and check to see whether or not the issue has been fixed when it boots up.

Solution 6: Roll back to the Windows 10 build you were previously using

If nothing so far has worked for you, fear not – you can simply roll back to the Windows 10 build that you were using before you downloaded and installed the Creators Update and wait for Microsoft to get around to fixing this annoying little issue, after which you can reinstall the Creators Update. Provided that it hasn’t been 30 days since you installed the Creators Update (at which point your computer deletes the installation files required for the rollback), the process should be quick and easy. In order to roll back to the Windows 10 build that you were previously using, you need to

At the login screen HOLD the SHIFT key and click the Power (icon) located on the lower right corner. Whilst still Holding the SHIFT key choose Restart.

Once the System boots into the Advanced Mode, choose Troubleshoot and then choose Advanced Options. From Advanced Options, choose the option titled Go back to previous build.

After a few seconds, you will be asked to choose your User Account. Click on the User Account, key in your password and choose Continue. Once done, choose the option Go Back to Previous Build again.