windows 10 enterprise not activated after build update to 9860 what the title said people, got the key and tried to activate and got this: --------------------------- Windows Script Host --------------------------- Activating Windows(R), Enterprise edition (72e02447-a7bc-462c-9c3d-e5c919a5140a) ... Error: 0x80072F8F On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x80072F8F' to display the error text. --------------------------- OK --------------------------- please help! thank you
Sorry to ask that, bu i didn't found the reg file in order to be able to update my Windows 10. Download is OK, but unable to install with the code 0x80070032. Anyone could help me please ? Thanks a lot
Did you make update or clean install ? because if build 9841 activated, not must be problem after updating to 9860.
@scandal1981 I have merged the thread. You can always try phone activation (& even if use existing KMS activators which isn't supported by Microsoft). Seems that activation servers can't be contacted from your place.
@tito thanks man I didn't know It goes here keep up the good work! to everyone else: phone activation worked great if anyone has same problem with activation apparently happens with updating builds not with fresh 9860 install
The upgrade process resets Windows RE and adds setosimage to point to the install.esd in that folder for System Refresh/Reset. It also can register the new winre.wim to C:\Recovery instead of upgrading the system RE tools partition (presumably due to a bug). Better to keep that folder, along with the $UPG$PBR.MARKER file in the root of the drive, see the textfile in the RecoveryImage folder. Though if you don't plan to use System Refresh/Reset, you can remove the RecoveryImage folder and the marker Redeploy WinRE. Mount the RE Tools partition in diskmgmt.msc, assign a letter (e.g. T: ), then copy C:\Recovery\winre.wim to another place to avoid it's deletion (during the reagentc /disable command ) then in elevated console use reagentc for redeployment Code: reagentc /info reagentc /disable md T:\Recovery\WindowsRE copy path\to\saved\winre.wim T:\Recovery\WindowsRE\winre.wim reagentc /setreimage /path T:\Recovery\WindowsRE /target C:\Windows reagentc /enable reagentc /info bcdedit /enum all Unmount the partition (remove the letter) and repeat the last command to verify. In {current} , recoverysequence must match the recovery section identifier , whose device shall point to the unmounted partition you saved winre.wim to, in the format of e.g. [\Device\HarddiskVolume1] P.S.: you can ignore the leftover recovery identifiers used by the previous system (not sure how to remove them, bcdedit /delete doesn't do it, and easybcd doesn't see recovery identifiers), and the Device options sections on the bottom
Because you don't have the right permissions to do so, you can get permissions by running the following command in an elevated command prompt: Code: takeown -f "C:\RecoveryImage\" -r (while you're at it, try the new command prompt features like copy/paste ) EDIT: Yeah, what Arseny92 said
As long as you use the provided Standard P-Key, online activation will work all times. I used that on my own Machine 5 times and several Friends machines. There isn't any need for to use Phone Activation!
@zimu000 We can't allow sharing these ISOs as each ISO created from the ESDs are different & thus considered as homebrew.
Plus there would be no way of evaluating the contents simply. Someone could insert some really bad malware and you'd never know without mounting the various files and comparing each file.
I couldn't agree more. Windows 10 is of no use until it reached beta level, except for maybe checking it out for a day or so to provide some (hopefully valuable) feedback. This is not meant for end-users, I'd say it's not even meant for developers as there is no updated SDK documentation about new APIs etc. available at the moment. So from a developer's standpoint, considering software development, this technical preview is no different from Windows 8.1. You currently can't do anything on Windows 10 what you cannot already do on Windows 8.1. Well, maybe you could, but then you would have to spend (or waste) your precious time figuring out how some of the new stuff works on your own, but it will be just a waste of time since there are no features locked down and you can't be sure if one of the new APIs will still be available or in its current shape for the next build. No, for the time being, Windows 10 is nothing more than Windows 8.1 with a few alpha-level, and therefore half-broken and ugly looking, additional features.You just have to look at the top 10 of feedback to figure out that Microsoft is getting a lot of feedback from people who are not really the target group of this insider program. But I guess that's just what happens when you're crowdsourcing your own dogfooding process.
A reminder to all those who say its not much different from windows 8.1 so it shouldnt exist or be like it: its going to be released in summer 2015 (about a year of development left and we are still at the beginning so no new UI changes as these come last). As for those who say this is not for tech enthusiasts, 1st microsoft marketed insiders as such and there is a reason for that, they want opinions from those who believe they are tech knowledgable because these are the ones with self inflated opinions on windows 8 and resisted the change to windows 8.1 and 2nd to mass test the new update ways which are NOT just for the beta which vali20 should've read by now being a tech savy guy Although i agree this preview is not for everyone out there: ie those complaining about telemetry, that their explorer gives an error when shutting down or that windows 10 looks like w8.1 and is featureless (there is a reason for that people wake up only 20 days have passed from build 9841 dont expect to see all your feedback even a remote feedback being used on this build) or even that the "new ui" sucks so it needs updating.