I learned that from Slave77, in Win 8.1 if I ever had errors in sfc I ran restore Health and it always fixed it, if I ran sfc again, no errors, works in Win 10 To, Slave77 has pee peed on my leg a bunch of times
...report "As the Windows 10 ship draws close to port, we’ve seen confirmation from multiple sources that yes, Windows 10 Build 10240 is the RTM version that was sent out to OEMs for installation"... Hispa
But the one sent out to OEM is not the same as first page, the first page is newer has updates added, you cannot update computer from old OEM, then Clean install with new image or I could not
I do not think so, updates were added after it went to OEM's, it is not the same image as in FaiKee's thread with OEM image, what I am trying to say is you must Upgrade and clean install with same image, no mixing.
I upgraded with FaiKee's image, activated, then used MS tool to download ISO to clean install, no activation, had to put 8.1 back on, well do over, this time from 1 ISO
Wow is this true? I'm now 99% sure (100% before reading your post) that did a clean install with a different image and had no problems, it activated.
Most of the images on 29 Jul were the same, im saying older images such as FaiKee's image you upgraded with, then used a image from Jul 29 did not work for me.
Nah, not suddenly, in 180 days from now . But is indeed offline: Code: ███████████████████████████████████████████████████████████████████████████████████████ KMS Client Emulator at: [kms.xspace.in] : [1688] ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Starting online test: 02.08.2015 at: 5:59:13,76 ---- KMS Host for: Windows8 ---------------- KMS Port: 1688 KMS Host: kms.xspace.in KMS Client Mode: Windows8 KMS Client Emulator started successfully. Runtime reported exception 0x6ba = 1722 ---- KMS Host for: Office2010 -------------- KMS Port: 1688 KMS Host: kms.xspace.in KMS Client Mode: Office2010 KMS Client Emulator started successfully. Runtime reported exception 0x6ba = 1722 ---- KMS Host for: Office2013V5 ------------ KMS Port: 1688 KMS Host: kms.xspace.in KMS Client Mode: Office2013V5 KMS Client Emulator started successfully. Runtime reported exception 0x6ba = 1722 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀