MSFT acknowledges some Win10 Pro licenses being mistakenly deactivated

Page 11 of 18 FirstFirst ... 910111213 ... LastLast

  1. Posts : 10,740
    Windows 11 Workstation x64
    Thread Starter
       #100

    I'm all for more screwups from MSFT like yesterdays
      My Computers


  2. Posts : 11,247
    Windows / Linux : Arch Linux
       #101

    z3r010 said:
    I'm all for more screwups from MSFT like yesterdays
    Hi there
    I bet Forum activity was quite busy yesterday !!!!

    Cheers
    jimbo
      My Computer


  3. Posts : 134,318
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #102

    z3r010 said:
    I'm all for more screwups from MSFT like yesterdays
      My Computers


  4. Posts : 579
    Windows 10
       #103

    cereberus said:
    But it was not critical. Comparing apples and oranges is fruitless.
    But it could have been, because Windows could refuse to Load beyond the Log-In Screen, as it happens after a Time.
    Lets face it seriously and practically, aside from "Mathematical Probabilities" or any other "Imagination Scenarios" .
      My Computer


  5. Posts : 913
    CP/M
       #104

    cereberus said:
    After any incident, it is normal to do am investigation and ascertain root causes, lesson learned, way forward etc. This takes time. At best, in one day, all you will get is a holding statement which was issued i.e. it is an emerging issue. If nothing is explained in a few days time that is unacceptable. It is too soon to say it is unacceptable at the moment until tbe facts are fully known and appropriate remediation steps are outlined above in principle.

    Yesterday of average admin:
    - 50+ calls and mails of affected users from early morning
    - investigating what is going on
    - testing in VM
    - searching the web for further info
    - communicating with management
    - composing apologetic message to all employees
    - replying to questions when it will be ok
    - trying & waiting for resolution
    All done for reason of incompetence of someone else.... Nobody expects the final statement instantly but short official explanation & apology is needed in this situation.

    Little explanation: once activated Win10 system remains in this state at least six months after activation (for example, if it has no access to activation servers). So the problem was wrong function of activation servers, not their inaccessibility. Under these circumstances, the first thing necessary to do is disabling malfunctioning service which harms other systems. But MS continued to de-activate PCs of customers all the day... Unbelievable.
      My Computer


  6. Posts : 15,485
    Windows10
       #105

    muchomurka said:
    Yesterday of average admin:
    - 50+ calls and mails of affected users from early morning
    - investigating what is going on
    - testing in VM
    - searching the web for further info
    - communicating with management
    - composing apologetic message to all employees
    - replying to questions when it will be ok
    - trying & waiting for resolution
    All done for reason of incompetence of someone else.... Nobody expects the final statement instantly but short official explanation & apology is needed in this situation.

    Little explanation: once activated Win10 system remains in this state at least six months after activation (for example, if it has no access to activation servers). So the problem was wrong function of activation servers, not their inaccessibility. Under these circumstances, the first thing necessary to do is disabling malfunctioning service which harms other systems. But MS continued to de-activate PCs of customers all the day... Unbelievable.
    Within a couple of hours an emerging issue statement was issued. It was middle of night, Redmond time! Your expectations are rather unrealistic. The issue was fixed before they probably had time to issue a formal statement. Corporate inertia is always pretty slow in any large organisation. It takes time to get statements approved. Best we get usually is vague twitter responses.
      My Computer


  7. Posts : 56,830
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #106

    cereberus said:
    Within a couple of hours an emerging issue statement was issued. It was middle of night, Redmond time! Your expectations are rather unrealistic. The issue was fixed before they probably had time to issue a formal statement. Corporate inertia is always pretty slow in any large organisation. It takes time to get statements approved. Best we get usually is vague twitter responses.
      My Computers


  8. Posts : 750
    Windows 10 Pro 64-bits
       #107

    muchomurka said:
    Yesterday of average admin:
    - 50+ calls and mails of affected users from early morning
    - investigating what is going on
    - testing in VM
    - searching the web for further info
    - communicating with management
    - composing apologetic message to all employees
    - replying to questions when it will be ok
    - trying & waiting for resolution
    All done for reason of incompetence of someone else.... Nobody expects the final statement instantly but short official explanation & apology is needed in this situation.

    Little explanation: once activated Win10 system remains in this state at least six months after activation (for example, if it has no access to activation servers). So the problem was wrong function of activation servers, not their inaccessibility. Under these circumstances, the first thing necessary to do is disabling malfunctioning service which harms other systems. But MS continued to de-activate PCs of customers all the day... Unbelievable.
    I've been looking at this along the same line...

    This has not been a server reliability issue, it's been a server configuration issue that had not been properly tested prior to rolling it out to production.

    This just shows that the Q&A, or lack of, doesn't only impact Windows feature updates. The very same lackadaisical Q&A process is in place for the internal MS servers as well.
      My Computer


  9. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #108

    Cr00zng said:
    I've been looking at this along the same line...

    This has not been a server reliability issue, it's been a server configuration issue that had not been properly tested prior to rolling it out to production.

    This just shows that the Q&A, or lack of, doesn't only impact Windows feature updates. The very same lackadaisical Q&A process is in place for the internal MS servers as well.
    Yep. I fully agree!
      My Computers


  10. Posts : 179
    Windows 11 Pro
       #109

    My faith in MS has been shakened lately. It's like they have students working on programming for Windows 10.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:14.
Find Us




Windows 10 Forums