Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

XP not activated, but it is!

  • 14-11-2006 3:02am
    #1
    [Deleted User]
    Posts: 0 ✭


    I installed a fresh copy of XP Professional (OEM) on my laptop on November 2nd. Every day since, in my application log in the Event Viewer, I see the following warning:

    Source: Windows Product Activation
    Event ID: 1005
    Your Windows product has not been activated with Microsoft yet. Please use the Product Activation Wizard within 30 days.

    The thing is, I activated Windows after installing all my drivers, and running msoobe.exe /a says that my system is already activated. A new warning is generated every day but the number of days in the message doesn't change - it's always at 30.

    Does anyone know what's going on here?


Comments

  • #2
    Ginger
    Registered Users, Registered Users 2 Posts: 2,931 ✭✭✭Ginger


    Possibly the best thing is to invalidate it and then revalidate it

    http://articles.techrepublic.com.com/5100-1035_11-5034890.html


  • #3
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    Thanks, but that link didn't work to deactivate it (I think that procedure only works for volume licence installs). I instead deleted the wpa.bak and wpa.dbl files - that did the trick.

    Since reactivation I haven't received any errors (yet). Hopefully it'll stay that way.


  • #4
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    No good, got another one at 22:50 tonight. :mad:


  • #5
    [Deleted User]
    Posts: 0 ✭ [Deleted User]


    I finally found the cause of this annoyance. It seems to be a regression problem with the 307154 hotfix. As soon as I removed the fix the errors stopped.

    So now I'm not surprised they never publically released it.


Advertisement