DISCUSSION: Windows 8.1 Spring 2014 Update RTM

Finally found some time to play with a latest leak. Successfully installed all 6 updates on VM running previous leak. Everything went smooth and fine and it seems that largest update installed faster this time.
Anyway, thanks to the guy who showed registry trick, to all who is sharing this update and to all MDL community.
Waiting for official release begins now.

 

u mean this isn't "official"?!?!






lol

 

You need to login to view this posts content.

 

If want your OS to be in other language then you need to install the language pack first. If you use en_US you obviously do not need any lang pack.

 

You can't change them.

 

2 times I tried to install the newest Update 1, both failed at 75%. Win 8.1 x64 and carefully followed the instructions. This time I'm gonna wait for the official release likewise. And you know what that meant... 2 new clean Win reinstallations.

The previous leak of Update I was able to install, but not this newest one.

Or at least I'm gonna wait for the "official" RTM leak.

 

Does this mean if you install Update 1, you can't install a language pack later?

I'm aware of how a language pack works (I think), but I'm seeing mixed reports of a language pack being installed and/or required for Update 1.

Does it just mean if I have a second language installed, that I need to download the language pack for it from WU before installing Update 1? Perhaps a better question might be... what relevance does a language pack and Update 1 have?

 

For those of you wondering how to check to see if its installed here you go...

reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "BuildLabEx"

This will out put the full version of Windows currently installed on your system.

You will see the following:

BuildLabEx_________REG_SZ___________9600.17031.amd64fre.winblue_gdr.140221-1952

The important part is the 9600.17031.amd64fre.winblue_gdr.140221-1952

The last part shows the build date aka 140221 or as we like to see it 2/21/14

Advise adding this to the original post.

 

Yeah, I know this update comes directly from M$ servers so from this point of view it is OFFICIAL. On the other hand, it wasn't released for public use yet. We even don't know for sure if this update is RTM. I know, that WZor and others state is RTM, but you never can be sure then we're talking about M$. So at this point I won't be installing leaked update on my main system, only on VM. And by saying that "I'll wait for official release" I mean, that I'll wait till it comes through Windows update.

 

You need to login to view this posts content.

 

Maybe the registry hack is working again?

 

It already did.

 

That would mean MS enabled it again, why would they do that?

 

did anyone check the hashes prior to removing them and after. Perhaps they changed something? Or maybe just had a change of heart.. wait.. this is MS.. nm..

 

New links are being traced, any pirates get Men in Black at their door

 

C'mon man! You know what I mean. Public Windows update, not some registry hack enabled Windows update for testers.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

The sha1 hash is at the end of the filename.

 

I've tried the following ways:
first I installed KB2919442 and KB2939087 and the update KB2919355 failed, then I read someone installed also KB2932046, so I did it but the installation of KB2919355 failed again, then I read that someone else installed all the updates and the big one at the end, but no way, it failed again...