Shortly after I upgraded from Windows 8.1 to Windows 10, I installed Microsoft SQL Server 2014 on my Asus laptop. The application ran just fine until I installed the latest Windows 10 update in November.
When I tried to run the SQL Server 2014 Management Studio, I received an error message about MSVCP100.dll being missing. After searching the Internet for answers, I followed the recommended solution: I installed the Microsoft Visual C++ 2010 Redistributable Package, which didn't fix anything. Then I manually downloaded 64-bit versions of MSVCP100.dll and a related missing DLL and copied them into the SysWow64 folder. After trying this solution, SQL Server 2014 still didn't run, and instead I got a different error message:
"The application was unable to start correctly (0xc000007b). Click OK to close the application."
I've tried a few other recommended solutions. Today I ran "sfc /scannow" from the Command Prompt, but it found no integrity violations.
I don't use SQL Server too often, but I need to be able to access the application, since I use it in my current job. I would rather not have to reinstall SQL Server, since this process takes several hours and won't necessarily fix dependency problems. What steps should I try next? Thanks for your help.
When I tried to run the SQL Server 2014 Management Studio, I received an error message about MSVCP100.dll being missing. After searching the Internet for answers, I followed the recommended solution: I installed the Microsoft Visual C++ 2010 Redistributable Package, which didn't fix anything. Then I manually downloaded 64-bit versions of MSVCP100.dll and a related missing DLL and copied them into the SysWow64 folder. After trying this solution, SQL Server 2014 still didn't run, and instead I got a different error message:
"The application was unable to start correctly (0xc000007b). Click OK to close the application."
I've tried a few other recommended solutions. Today I ran "sfc /scannow" from the Command Prompt, but it found no integrity violations.
I don't use SQL Server too often, but I need to be able to access the application, since I use it in my current job. I would rather not have to reinstall SQL Server, since this process takes several hours and won't necessarily fix dependency problems. What steps should I try next? Thanks for your help.