cscript ospp.vbs /ddescr:##..##

Anonymous
2024-03-04T18:35:53+00:00

When I execute this script using an ADMIN command prompt:

cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /ddescr:0x8007007B

I get a not-very-helpful error window stating that "an error has occurred".

What should I do?
Thanks,
Dan

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-04T20:58:11+00:00

    Hello Danny,

    I'm Ibhadighi and I'd happily help you with your question. In this forum, we are Microsoft consumers just like yourself.

    The error code 0x8007007B typically indicates an issue with Windows activation that usually relates to the KMS (Key Management Service) configuration. If you're seeing this while trying to use the ospp.vbs script to manage the activation of an Office product, here are some steps you can take:

    1. Ensure that the KMS host is accessible and that your machine can communicate with it.
    2. Confirm that your version of Office is indeed a volume license edition that requires activation via KMS.
    3. Ensure that the command prompt is opened with administrator rights (which you've done).
    4. Confirm the path to ospp.vbs is correct and that the file exists at that location.
    5. Make sure your computer has a stable internet connection to reach Microsoft's activation servers if you are not using a KMS host.
    6. If you're on a company network, make sure that the firewall or network policies are not blocking access to the KMS service.

    Make sure that all commands are typed correctly and that you're using the correct activation key for your Office installation. If you've recently made changes to your system's hardware or reinstalled Windows, this might also affect activation.

    I hope this helps.

    Best Regards, Ibhadighi

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-03-05T00:52:08+00:00

    Hi Dighi,

    I did try everything you suggested before submitting my question, and I can get other ospp commands (like dstatus).

    But I cannot get /ddescr:0x8007007B or any other 0x-error code to work.

    So it's getting /ddescr: that appears to be a "broken flag" on the ospp command.

    Once again, all other flags I've used with ospp work fine.

    Thanks,

    Dan

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-03-05T23:26:46+00:00

    Hello Danny,

    Unfortunately, I’m really sorry I don't have any further troubleshooting to offer.

    There are many knowledgeable users active on the forum and I hope that someone else can offer further insight into your issue.

    Thank you, Ibhadighi

    0 comments No comments
  4. Anonymous
    2024-03-06T05:18:49+00:00

    Hi Dighi,

    Thank you for your reply, but the problem has been solved in another forum where I posed this question.

    Surprisingly, it turns out that the answer was staring me in the face: THERE WAS NO PROBLEM!

    When issuing the command I originally posed, the following image is displayed:

    and upon clicking on SEE DETAILS, the desired error text is revealed!

    So the answer was there but I was fooled by the unexpected error window.

    Thanks very much for your followup.

    Dan

    0 comments No comments
  5. Anonymous
    2024-06-13T13:05:59+00:00

    ERROR CODE: 0x8007007B

    ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x8007007B

    0 comments No comments