SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Mike McFarland who wrote (90511)8/31/2015 8:30:16 AM
From: PMS Witch3 Recommendations

Recommended By
B.K.Myers
Eric L
goldworldnet

   of 110652
 
Windows 10 Product ID and Activation. . .

With Windows 10, Microsoft has altered how Product ID and Activation works Previously, for OEM systems, Activation depended on three parts: License code in the BIOS, a Software Certificate, and the Product Key. For Retail systems, only a valid Product Key was needed, but unlike OEM systems, these keys were unique for each system.

Re-Installing Windows was easy. OEM customers using disks from their systems' manufacturer didn't need to deal with activation. Their disk had the Certificate and Key, and their hardware had the correct BIOS code.

Retail customers could re-install easily too, as long as they had their Product Key. To Activate, their system would contact Microsoft, and if the hardware matched the original installation, Activation was automatic. If the hardware had changed "too much," these customers could telephone Microsoft for a new key. (Retail customers are allowed to "change" their hardware.)

How is Windows 10 different?

With Windows 10, Microsoft keeps a record of every system. When a customer re-installs Windows, their new system contacts Microsoft and sends off data that uniquely identifies their machine. If Microsoft accepts that Windows 10 was installed on the same machine, the code necessary for Activation is returned and the system becomes activated..

However, the conversion to this new Activation is not entirely complete. For example, Windows Installation still asks for Product Keys. As well, Product Keys are stored in the Registry in the same location and format used by previous versions of Windows. And of course, utilities for finding keys still find these keys. Trouble is, these keys cannot and will not Activate a Windows 10 system. Note: These keys will get you past a Windows Installer that won't proceed without a key being entered -- so they are still of some use!

Cheers, PW.

P.S. Clean Install Windows 10. . .

The "Official" way of performing a clean install of Windows 10 when upgrading from earlier Windows is to do the upgrade, let the new Windows 10 system Activate (and register with Microsoft,) and then replace this upgraded Windows 10 system with a new, clean, Windows 10. The clean Windows 10 will Activate because the system has been registered with Microsoft.

But there's a shortcut!

When Windows 10 Install upgrades your Windows, it first determines that you have a licensed copy of Windows that entitles you to the free upgrade. It does this by executing GatherOSState.EXE, a program found on the Windows 10 DVD. (On my DVD, it's found at G:\Sources\GatherOSState.EXE

GatherOSState.EXE creates a file, GenuineTicket.XML, and saves it in the folder from where it was executed. You'll need to save this file somewhere safe if you're planning on formatting your Windows volume prior to installing Windows 10.

The trick to doing a clean install is to first execute GatherOSState.EXE and save the GenuineTicket.XML file it creates. Then, after doing a clean installation of Windows 10, copy the GenuineTicket.XML file to your new system in this location:

C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\GenuineTicket.XML

With this file in place, go to Control Panel, System, and click on the link to Activate Windows. Within a few seconds, your system will be Activated. Note: During Activation, the GenuineTicket.XML file gets deleted.

Note: Because GatherOSState.EXE writes GenuineTicket.XML to the folder where it was executed, if you're using a DVD, you'll need to copy the file to a location where a file can be written.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext