I'm the administrator and simply run the command:

 sqllocaldb start v11.0


 Start of LocalDB instance "v11.0" failed because of the following error:
 Error occurred during LocalDB instance startup: SQL Server process failed to sta

Event viewer log Event ID: 528

Windows API call WaitForMultipleObjects returned error code: 575. Windows system error message is: {Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application. Reported at line: 3621.

I tried another (user and administrator) accounts, there were no problems with them.

I uninstalled & reinstalled 2012 version of SQLLocalDB.msi but I had no luck. Do you have any idea & fix?

  • Visual Studio had trouble starting my project and I saw the same error in the event log. Fixed it by running sqllocaldb start v11.0.
    – Andre Luus
    Commented Apr 9, 2013 at 6:51

10 Answers 10


Check the error log which usually under the folder %localappdata%\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0 will give you big hints.

Log back in as the administrator account (not an administrator), and start a command prompt with Run As Administrator. Then run this:

sqllocaldb share v11.0 MyInstance

You might want to explicitly add your Windows account as a sysadmin on this instance if that is a goal. So:

sqllocaldb start MyInstance

Then connect with SQLCMD, Management Studio, what have you, and run:

EXEC sp_addsrvrolemember N'Domain\Username', N'sysadmin';

Now log back in as your Windows account, and you should be able to start this instance using:

sqllocaldb start MyInstance

(It may already be started depending on your O/S and how you switched accounts.)

Then Domain\Username should be able to connect using SQLCMD, SSMS etc. using (localdb)\.\MyInstance.

  • 1
    This is a good workaround but it can't explain & solve the problem.
    – Nime Cloud
    Commented Dec 17, 2012 at 12:50
  • 1
    @NimeCloud um, ok, maybe someone else will come along with a better "fix." <shrug> Commented Dec 17, 2012 at 14:27
  • This worked for me. It was related to the original instance where the specific user has no grants anymore and weirdly it cannot give access to no matter what you do. The shared instance was treated as separate identity thus it was given a "fresh" start where the app can now connect like before.
    – Jon P
    Commented Feb 4, 2019 at 3:26

I logged off and then logged in as another administrator and renamed my user profile folder's name. I switched into my account in Windows 7. There is a newly created TEMP folder as my user profile folder. I compared before & after folder structure as in picture. Plus; LocalDB instance started successfully.


I logged off and renamed my username to original. Logged again & jumped into that folder:

C:\Users\MYUSERNAME\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0

And saw the error logs; Access denied!


Solution: Simply delete all files in v11.0 folder. Give write permision to v11.0 folder. If you can't create another instance give write permission to Instances folder.

  • 1
    Deleted the v11.0 folder. Then issued sqllocaldb.exe c v11.0 to recreate it (in VS2013 developer command line, elevated). This solved it. Commented Apr 21, 2015 at 17:16

I opened services.msc and restarted the following services:

  • Sql Server Browser
  • Sql Server VSS Writer

Hope it helps


I used to have this problem when my localdb and sql instance was installed with a different user than the current (domain user), so I fixed this by clearing the V11.0 folder and pasting the mdf and ldf files from the old path :

C:\Users\{inseryouroldusernamehere}\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0

Hope it helps.


I had this once and a simple reboot solved it. Seems to have solved it for other people too. Maybe worth attempting before doing Nime & Aarons answers


Create a file fix.bat, put the following text in it:

net localgroup Administrators "%userdomain%\%username%" /add

net localgroup Users "%userdomain%\%username%" /add

sqllocaldb d test

rd /s/q "%localappdata%\Microsoft\Microsoft SQL Server LocalDB\Instances\test"

sqllocaldb c test -s

Run fix.bat as the administrator then restart your computer. Run fix.bat again.

I have used this method to solve this problem over 10 times.


I am posting this here as this question is currently higher in Google search results than others. In my case LocalDB couldn't be started from IIS. I followed the this SO comment's suggestion to modify C:\Windows\System32\inetsrv\config\applicationHost.config to add setProfileEnvironment="true" to the App Pool as described in Using LocalDB with Full IIS, Part 1: User Profile. I actually changed the applicationPoolDefaults's processModel's setProfileEnvironment attribute to true and it worked as well which might be better so you don't need to remember to do it for every new App Pool.


If you don't have any real info in the localdb instance, you can simply delete it. This is a good choice if your database are automatically initialized (using EF DbInitializer or migrations etc.).

Here's what I did to resolve the issue:

  • Open a command prompt window
  • Execute sqllocaldb delete ****, where **** is either blank for the default instance (usually MSSqlLocalDb or the troublesome instance
  • Execute sqllocaldb create ****
  • Execute sqllocaldb start ****

This worked for me, but do this at your own risk and make sure to double check you have no valuable data in that instance, and ensure you perform the actions on the correct instance.


Had this issue on Windows 10 when our application was run with compatibility for Windows 8 enabled. Turning off the compatibility setting fixed it.


I came across this thread in trying to troubleshoot Veeam Agent service not starting. Walked thru manually creating database...which creates the data in: C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint for some reason. Delving into it's error log file, this was my culprit...

Cannot use file 'C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 32768. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

now on to veeam support to find a fix

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.