Screenshot leaked in January reveals Office 2010 activation period


Recommended Posts

How long could we play with the recently leaked Office 2010 build without activating it? I just find a screenshot of much earlier build of Office 2010, which could give us a hint on the activation period (about 30 days) without a product key. However, this may change in the leaked Office Technical Preview build. After the activation period expires, we know that the entire Office suite will become Office reader:) Maybe a "limit-less" way of experimenting Office 2010 is creating a virtual machine and making a guest OS snapshot:)

post-268740-1242565212_thumb.jpg

Am i missing something? I have Office 2010 and the Microsoft Word screen (your screen) it's different than mine...there is another leaked version beside the Tehnical one (newer one)?

27369556.th.png

The screenshot he is referring to is an old screenshot.

The leaked 'technical preview' of Office 2010 is an older version of the code as to what will be released to people who have signed up for the technical preview. It may be that everyone has to wait until then to find out what the activation period is one both builds.

  • 4 weeks later...

Will Office 2010 even be released this year?

At the very least, will there be a public beta later this year? I was hoping it'd be possible to replace the preview with a beta before it expires.

Will Office 2010 even be released this year?

At the very least, will there be a public beta later this year? I was hoping it'd be possible to replace the preview with a beta before it expires.

The beta will be out in July to selected testers and I wont be surprised if it leaks out.

Oddly enough, mine says 4 days remaining too. But it said 4 days remaining yesterday too. Did anyone's get to 3 days yet?

It said 4 days for me yesterday,a nd now i have only 3 days remaining. damn :p

Weirdly though, it didn't ask to activate before.

Bummer. So reinstalling 2010 won't reset the activation period? If it doesn't then there has to be a registry key that can be deleted to reset the trial. Unless, of course, the activation keeps track of the computers using the trial over the network.

I set my clock forward 1 week, and although I get the 'not activated' message when opening an Office app they continue to work just fine. So nothing to worry about! I then put the date back and I now have 3 days again, so seems this expiration is nothing more than a simple date check, which would probably be reset anyway by uninstalling / re-installing.

Anyway, no need to go backwards to O2007 :)

I set my clock forward 1 week, and although I get the 'not activated' message when opening an Office app they continue to work just fine. So nothing to worry about! I then put the date back and I now have 3 days again, so seems this expiration is nothing more than a simple date check, which would probably be reset anyway by uninstalling / re-installing.

Anyway, no need to go backwards to O2007 :)

Nope. I tried uninstalling and reinstalling, no dice.

As for the changing the clock time, it would be a pain to mess with that all the way. From what I notice, OSPPSVC.exe is responsible for the trial resetting. Office even automatically repairs itself when you delete this exe. Have to give props to MS for tightening up on freeloading. :p

I set my clock forward 1 week, and although I get the 'not activated' message when opening an Office app they continue to work just fine. So nothing to worry about! I then put the date back and I now have 3 days again, so seems this expiration is nothing more than a simple date check, which would probably be reset anyway by uninstalling / re-installing.

Anyway, no need to go backwards to O2007 :)

Ah thanks for the bright findings ;) That nag screen is not much of problem for me. And besides beta version is comming out soon, so we just have to stick with this version for a wee bit more.

But what is the impact of an expired copy? Seems to work just the same, so apart from the nag screen it's fine - I think?

If it is just a nag screen, then I guess it won't be a problem. I just don't hope it goes into a read-only mode or something. I got 3 days left, so guess most of us will find out soon.

I think I've managed to Rearm my copy of Office 2010 CTP.

dwGraceTime is a dword that holds the grace period before the software will stop working and require activation. This shows that I have 29 days 23 hours 53sec remaining now.

> GetLicensingStatus 59a52881-a989-479d-af46-f275c6370663  128a057a-7e95-4063-b2
96-c54c5f3d3f3a
SkuId			= 128a057a-7e95-4063-b296-c54c5f3d3f3a
eStatus		  = SL_LICENSING_STATUS_IN_GRACE_PERIOD
dwGraceTime	  = 29D 23:53
dwTotalGraceDays = 30 days
hrReason		 = 4004F00C
qwExpiration	 = 2010/10/31


OK.

>

The nag window with running timer has gone currently, so I'll know whether it comes back or not.

All I did was basically rearm the Office timer through the Office Protection Platform cmdline interface.

Stop the Office Software Protection Platform service first.

run C:\Windows\System32\OSPPRUN.exe.

>Initialize

>Open

>GetInstalledSkuIds
   0. 128a057a-7e95-4063-b296-c54c5f3d3f3a (you are interested in this one)
   1. 26adec89-edf3-4adc-a3fc-c865f1a9f71f

OK.

> GetInstalledAppIds 128a057a-7e95-4063-b296-c54c5f3d3f3a
   0. 59a52881-a989-479d-af46-f275c6370663

OK.

 (Will Look something like this if you have 1 day remaining)

> GetLicensingStatus 59a52881-a989-479d-af46-f275c6370663 128a057a-7e95-4063-b296-c54c5f3d3f3a
SkuId			= 128a057a-7e95-4063-b296-c54c5f3d3f3a
eStatus		  = SL_LICENSING_STATUS_IN_GRACE_PERIOD
dwGraceTime	  = 1D 23:37 
dwTotalGraceDays = 30 days
hrReason		 = 4004F00C
qwExpiration	 = 2010/10/31


OK.

(This rearms the AppId and specific SkuId for Office 2010 you are using, I think they should be the same for all, if not just replace it with what yours returns from the command)

> Rearm 59a52881-a989-479d-af46-f275c6370663 128a057a-7e95-4063-b296-c54c5f3d3f3a 1

OK.

>close

>Initialize

>open

Should Show something like the following now if it rearmed successfully! 

> GetLicensingStatus 59a52881-a989-479d-af46-f275c6370663 128a057a-7e95-4063-b296-c54c5f3d3f3a
SkuId			= 128a057a-7e95-4063-b296-c54c5f3d3f3a
eStatus		  = SL_LICENSING_STATUS_IN_GRACE_PERIOD
dwGraceTime	  = 29D 23:37
dwTotalGraceDays = 30 days
hrReason		 = 4004F00C
qwExpiration	 = 2010/10/31

>quit

This command shows remaining rearms.

> GetApplicationInformation 59a52881-a989-479d-af46-f275c6370663 RemainingRearmCount
(DWORD, []) 59a52881-a989-479d-af46-f275c6370663 = 4


OK.

This shows how many rearms you have performed.

> GetApplicationInformation 59a52881-a989-479d-af46-f275c6370663 RearmCount
(DWORD, []) 59a52881-a989-479d-af46-f275c6370663 = 1


OK.

I lost my buffer logs but I'm pretty certain this is the procedure I did step by step. I've tried to explain best I can.

At the > you can type "?" for help.

I don't know if this was intentional or not, to prevent the preview being used for more than 30 days but the following is why the nag screen has appeared :)

> ActivateProduct 128a057a-7e95-4063-b296-c54c5f3d3f3a

Error code hr = 0x8007232B,DNS name does not exist.

DNS entry for the activation server hostname doesn't exist on any Root DNS servers, so perhaps this was intentional :)

Edit: Oops forgot to mention make sure you launch Command Prompt with Elevated Privs otherwise you will get errors that you can't perform the operation.

Edited by mikeyakagod
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I've been on Deezer for over a decade, but glad that Tidal joined them in fighting AI slop. Can't stand such takes as Spotify's: "Spotify's CEO recently pushed back against listeners who call AI music "slop," urging people to stop using the term and instead embrace the creative potential of AI music."
    • “Could” … in the IS the healthcare is run by insurance companies that make indecent profits denying basic treatments to people that are paying money for nothing. Besides, where are all the Trump epigones who were stating that the tariffs were going to paid by foreign companies and not the US citizens? …
    • Microsoft Teams gets smarter at spotting sneaky meeting bots by Usama Jawad Microsoft Teams is set to receive a couple of new features soon, including a dedicated Recap app and a rather controversial location tracking functionality. The Redmond tech giant has also explained how it has made online communication and collaboration a lot more performant this year. Now, the company has detailed more secure bot admission mechanisms, as first reported by us in March 2026, and now available in Teams. As the use of AI has expanded across enterprise environments, Microsoft has begun allowing users to integrate bots into their meetings for various tasks, such as note-taking. While this has a tangible productivity benefit for users, Microsoft has highlighted how misconfiguration has allowed bots to join meetings that they shouldn't. This has created security and privacy risks, which Microsoft is now combating using a new Teams admin policy that allows organizers to control how external bots access meetings. Admins can leverage a policy called Manage external bots and their access to meetings. The default configuration is "When detected, require approval before joining", which places detected bots in a lobby before they are explicitly admitted into the meeting. The other option disables the experience. Microsoft has also requested admins to only allow organizers and co-organizers to manage access to a meeting, so that other people don't randomly allow bots into meetings. Teams will now be able to leverage infrastructure signals to intelligently detect and distinguish between bots and humans. Microsoft will soon also trial a registration experience for independent software vendors (ISVs) to build a system that registers a bot with Microsoft, so it is marked as a "known" bot. Teams will also categorize bots as trusted and suspected threats so that organizers can quickly identify which bots they want to allow into a meeting. Additional safeguards to block accidental admission of a bot into a meeting include: No one-click Admit option for identified bots Confirmation prompts when admitting participants that include bots Warnings when organizers choose Admit all, and bots are included Microsoft has begun rolling out this experience, and it will be retiring the current CAPTCHA verification implementation. In the future, the company plans to roll out new capabilities like allow-lists, organization-wide policies, admin reports, audit logs, and more granular controls.
    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      538
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!