To fix this, the corrupted system file, nlasvc.dll, needs to be replaced with a working version of the file.
If you need to delete or overwrite a system file in Windows Vista, you'll notice that you cannot delete system files, even as administrator. This is because Windows Vista's system files are owned by the TrustedInstaller service by default and Windows File Protection will keep them from being overwritten.
However, there is a way that you can get around this: you need to take ownership of the files, and then assign yourself rights to delete or modify the file. For this, you can use the command line:
First, open an administrator command prompt by typing cmd into the start menu search box, and hit the Ctrl+Shift+Enter key combination.
To take ownership of the file, you'll need to use the takeown command.
At the command prompt type: takeown /f c:\windows\system32\nlasvc.dll
That will give you ownership of the file, but you still have no rights to delete, move and rename it. Next, you need to run the cacls command to give yourself full control rights to the file:
At the command prompt type: cacls c:\windows\system32\nlasvc.dll /G your username:F
Make sure that you replace "your username" with your username exactly as it is spelled for the currently active user account on your computer.
At this point, you should be able to change the file. Rename the file from nlasvc.dll to nlasvc.dll.old. Next, copy the new source file that you downloaded from above to c:\windows\system32.
You can copy the nlasvc.dll file from your working laptop, or you can download it from https://www.dllme.com/dll/files/nlasvc_dll.html
Once the file has been replaced you need to set the permissions back to its original state. Locate nlasvc.dll in c:\windows\system32 in the Windows File Manager. Right mouse button click on the file and choose Properties.
Click Security tab; Click Advanced button; Click Owner tab; Click Edit button; Click Other User or Group and type in NT SERVICE\TrustedInstaller.
Press Ok on all dialogs until all property dialogs are closed. Restart the PC and all should be good again.