So now I'm pretty sure my Software licensing service is damage; when attempting to start the service (It has been stopped, which I think is what my problem), I get an error message:

Windows could not start the software licensing service on local computer.

Error 0xd0000022:0xd0000022


Is there a way to repair that?

With Administrative rights go to C:\windows\, right click the system32 folder, select properties and clear the 'read only' chech box.
Click apply, then Ok!

By selecting the main System32 folder and making it read/write, Windows resets those folders back to their initial read/write status.

Then go through these steps again to try and initiate the SL service again:

Open a command prompt and run as administrator

Type: net start slsvc

If you do not have access to the Start button:

Click the option 'Access computer with reduced functionality' and a Browser should open, type: %windir%\system32 into the address field.

Find the file cmd.exe

Right Click on the cmd.exe and select Run as Administrator

Type: net start slsvc

You could also create a support request at http://go.microsoft.com/fwlink/?linkid=52029 for more assistance starting the Software Licensing Service......thats if you like dealing with tech support guys which is sorta like removing wisdom teeth with no anesthetic.

Regards

Had the exact same problem. I called Microsoft Vista SP1 support line 1-866-234-6020 , and they solved it for me.

At 8/8/08 3:00am, Vista initiate a windows update.

At 3:06am, Vista initiated a reboot

At 3:12am, Vista damaged its licensing token

Here’s the solution:


command prompt with admin rights:

Net stop slsvc (it was already stopped)

Cd\windows\serviceprofiles\networkservice\appdata\roaming\microsoft\softwarelicensing


Ren tokens.dat tokens.bad

Net start slsvc

Cd\windows\system32

SLMGR.vbs - rilc

Reboot

Enter vista product key and let it activate:


Reboot again

I'm completely disgusted with Vista / Mojave

I am happy to report that this solution, even after 2 years, still works beautifully. Iam surprised how vulnerable Vista is ... a botched Apple Safari install caused all this... Or simple uninstalling bloatware caused this. I found all this here: I followed this, but yours looks even simpler.