Hi @murphy78! I downloaded esd file. I checked SHA1 hash and that is correct. But when i used esd-decrypter-wimlib-6 to build iso file, the SHA1 of ESD file was changed. Why? is that OK? Is the iso file created correctly??
I have a tablet with with genuine win 8.1, do I need to use the home version? I did try it in vmware with a year old machine with 8.1 pro and upgrade went fine there
yes after the esd is decrypted, the hash changes. That is why it is important to make a copy of the ESD if anyone plans to upload it somewhere to mirror. OR everyone gets a funky hash and starts yellin FAKE FAKE FAKE. If the hash was right when you started, its good and so is the ISO. Just don't share the ESD now (or ISO!) lol I see it just fine.
the hash has to change, the file (ESD) is being changed by being decrypted. IT cannot stay the same and be changed at the same time. Kinda like pealing a fruit but not? err something.
It is impossible if the process has been done according to instruction. Abbody1406 always have the original ESD backuped, and rename it upon completion of the process when you press Enter.
Is anyone not getting their copies activated? I upgraded my "boot to VHD" copy in VM mode to 10240 and it seemed activated but when I booted to it it was no longer accepting the key. Anyone know what is going on? edit: I should have realised that it links to the MS account and that they have currently switched off the linkage for new devices.
Could someone please help me remove these throw PowerShell .. Thanks by the way Name : Microsoft.WindowsFeedback Publisher : CN=Microsoft Windows, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Architecture : Neutral ResourceId : neutral Version : 10.0.10240.16384 PackageFullName : Microsoft.WindowsFeedback_10.0.10240.16384_neutral_neutral_cw5n1h2txyewy InstallLocation : C:\Windows\SystemApps\WindowsFeedback_cw5n1h2txyewy IsFramework : False PackageFamilyName : Microsoft.WindowsFeedback_cw5n1h2txyewy PublisherId : cw5n1h2txyewy PackageUserInformation : {S-1-5-21-2777683157-1550610358-3678770436-1001 [S-1-5-21-2777683157-1550610358-3678770436-1001]: Installed, S-1-5-21-2777683157-1550610358-3678770436-1002 [Nicolas]: Installed} IsResourcePackage : False IsBundle : False IsDevelopmentMode : False Name : Windows.ContactSupport Publisher : CN=Microsoft Windows, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Architecture : Neutral ResourceId : neutral Version : 10.0.10240.16384 PackageFullName : Windows.ContactSupport_10.0.10240.16384_neutral_neutral_cw5n1h2txyewy InstallLocation : C:\Windows\SystemApps\ContactSupport_cw5n1h2txyewy IsFramework : False PackageFamilyName : Windows.ContactSupport_cw5n1h2txyewy PublisherId : cw5n1h2txyewy PackageUserInformation : {S-1-5-21-2777683157-1550610358-3678770436-1001 [S-1-5-21-2777683157-1550610358-3678770436-1001]: Installed, S-1-5-21-2777683157-1550610358-3678770436-1002 [Nicolas]: Installed} IsResourcePackage : False IsBundle : False IsDevelopmentMode : False
I'm not certain but I think yes - keys will no longer be accepted. Someone will need to confirm. Edit: No it's not too late for a solution. If you have borked the upgrade then KMS activation is still an option for you.
Confirmed.... New VM 10166 (generic key unactivated) to 10240 with generic key yesterday blocked. This is with insider account logon.
Several have posted that they have done it fine haven't they? There's an active online host activating KMS clients. Will try and find it and edit this post, if not can someone else post it plz? Edit: Working KMS server... Spoiler Code: kms.xspace.in
(sorry had to get rid of the link) red d or c blue replace with what lang you want And don`t forget to add the .cab at the end. Worked just fine 1 minute ago.