Windows 8.1 RTM Released to MSDN & Technet

Windows 8.1 is now available for download from Technet & MSDN

Based on the feedback from you and our partners, we’re pleased to announce that we will be making available our current Windows 8.1 and Windows 8.1 Pro RTM builds (as well as Windows Server 2012 R2 RTM builds) to the developer and IT professional communities via MSDN and TechNet subscriptions. The current Windows 8.1 Enterprise RTM build will be available through MSDN and TechNet for businesses later this month. For developers, we are also making available the Visual Studio 2013 Release Candidate, which you can download here. For more on building and testing apps for Windows 8.1, head on over to today’s blog post from Steve Guggenheimer.

More...

 

[Ex_Brit]

What I'll work on tomorrow will be trying to change my primary account from a Microsoft account to a local account--Microsoft seems to have made that a bit more complex than it was in 8.0, where it was fairly easy to do that, I thought.

Yes they have and I'm trying to figure that one out too.

 

[Ex_Brit]

OK to anyone using a Microsoft account it's easy to switch to a local one. Just bring up the Charms bar > Settings > Change PC Settings > Accounts and click Disconnect and then all will be revealed.

http://www.eightforums.com/tutorials/4842-local-account-switch-windows-8-a.html

 

[Wds]

Hi All

When i update from wds 8 to 8.1 ..

Do I have to set up all over again ? .. like new windows ...?

Thanks .

 

[Ex_Brit]

You shouldn't have to if you elect to keep your settings.

 

[floepie]

I took a clean install, the 8.0 OEM key wasn't accepted (I had a key prompt which I skipped) but the OEM key it was already inserted. Just needed to activate online. :thumb:
If you need to re-insert it manually, do that. If it fails it might already be inserted.

All good.

Needed to mess around a bit so I also did the install in a VirtualBox 4.3 Beta but I had bluescreens due to VBox being unstable; VM VT-x instabilities.

The OS works fine and I like the new colored tiles.

Looks like the default Windows theme is pretty orange-yellowish, just to my liking and that was a surprise.

Not sure if I understand. How did you bypass the key prompt? I have a new W8 laptop with the BIOS key, so I'm assuming that mine, like yours, will also get its BIOS key recognized somewhere during the install. When I attempted to install, I didn't see a way around the key prompt.

 

[SIW2]

It seems others are doing this:

You need a key to install it.

Bottom of the first post http://www.eightforums.com/windows-...1-rtm-core-pro-enterprise-x86-x64-leaked.html

You then need to enter your oem key to activate - better find out what that is first.

 

[Hopachi]

I took a clean install, the 8.0 OEM key wasn't accepted (I had a key prompt which I skipped) but the OEM key it was already inserted. Just needed to activate online. :thumb:
If you need to re-insert it manually, do that. If it fails it might already be inserted.

All good.

Needed to mess around a bit so I also did the install in a VirtualBox 4.3 Beta but I had bluescreens due to VBox being unstable; VM VT-x instabilities.

The OS works fine and I like the new colored tiles.

Looks like the default Windows theme is pretty orange-yellowish, just to my liking and that was a surprise.

The product key field was blank for me. I never thought to try skipping it. I don't know what my embedded code is. The script I ran only showed my Media Center key when I ran it, not the embedded key. In a way it actually made things quicker and simpler for me. My embedded code is for 8 core, so I end up upgrading to 8 Pro and then doing it again to add media center. I got to skip one step and install 8.1 Pro. Then do the one add features to add Media Center.

I've created a custom ISO where Core version is selectable and key prompt can be skipped (it will prompt it again before user setup anyway *).

I kept using Core and noted the key down after using one of those vbs-scripts to show it.

After the install of 8.1:
* It showed a blank key as well but when I tried to insert it it gave an error... then I check system properties and it was already inserted. A glitch maybe?

As I said, in the end all went well.

In your case it would be nicer to note the key down so that clean installs prompts will be dealt with.
Even better would it be your own custom PRO Media Center ISO so that you clean-install all in one step.

 

[Hopachi]

Not sure if I understand. How did you bypass the key prompt? I have a new W8 laptop with the BIOS key, so I'm assuming that mine, like yours, will also get its BIOS key recognized somewhere during the install. When I attempted to install, I didn't see a way around the key prompt.

Since I'm still using the laptop's OEM license:
I use the 8.1 Core version, to match the one the OEM installed for 8.0.

For this you need to make a custom ISO where you can select Core version (Pro will be also listed below). This will also skip the key prompt before install.

About that custom ISO:

It contains one extra file in the sources folder, that's all.

Version selection menu:
You don't actually need an ISO in the end if you boot from USB, just put the files on USB stick and in the sources folder, one extra file called "ei.cfg" with the following options in it:

[Channel]
OEM


[VL]
0

 

[alphanumeric]

I took a clean install, the 8.0 OEM key wasn't accepted (I had a key prompt which I skipped) but the OEM key it was already inserted. Just needed to activate online. :thumb:
If you need to re-insert it manually, do that. If it fails it might already be inserted.

All good.

Needed to mess around a bit so I also did the install in a VirtualBox 4.3 Beta but I had bluescreens due to VBox being unstable; VM VT-x instabilities.

The OS works fine and I like the new colored tiles.

Looks like the default Windows theme is pretty orange-yellowish, just to my liking and that was a surprise.

The product key field was blank for me. I never thought to try skipping it. I don't know what my embedded code is. The script I ran only showed my Media Center key when I ran it, not the embedded key. In a way it actually made things quicker and simpler for me. My embedded code is for 8 core, so I end up upgrading to 8 Pro and then doing it again to add media center. I got to skip one step and install 8.1 Pro. Then do the one add features to add Media Center.

I've created a custom ISO where Core version is selectable and key prompt can be skipped (it will prompt it again before user setup anyway *).

I kept using Core and noted the key down after using one of those vbs-scripts to show it.

After the install of 8.1:
* It showed a blank key as well but when I tried to insert it it gave an error... then I check system properties and it was already inserted. A glitch maybe?

As I said, in the end all went well.

In your case it would be nicer to note the key down so that clean installs prompts will be dealt with.
Even better would it be your own custom PRO Media Center ISO so that you clean-install all in one step.

Yeah, but how do I get my embedded code now? The vbs script is just going to display the product code currently in use. In my case that will be my Media Center key. That's what I got the last time I ran a scrip that was floating around here.

 

[Hopachi]

Yeah, but how do I get my embedded code now? The vbs script is just going to display the product code currently in use. In my case that will be my Media Center key. That's what I got the last time I ran a scrip that was floating around here.

I ran it while OEM version was still installed, for backup purposes since I've expected key prompts like now. Didn't trusted the "automatic" system: key has to be shown somewhere and that's why I stepped in in time to retrieve it for my clean installs.

Probably the BIOS doesn't display it (possible hidden menu's...) and you might try all boot prompts F1 to F12 for extra options.
The Recovery partition the manufacturer put on your disk drive has to contain the OEM key somewhere but I don't know where.

These are just some suggestions where to look, if the key is saved as most believe, there has to be a way to retrieve it. The vbs-script shows the currently installed version's key indeed.

 

[alphanumeric]

Yeah, but how do I get my embedded code now? The vbs script is just going to display the product code currently in use. In my case that will be my Media Center key. That's what I got the last time I ran a scrip that was floating around here.

I ran it while OEM version was still installed, for backup purposes since I've expected key prompts like now. Didn't trusted the "automatic" system: key has to be shown somewhere and that's why I stepped in in time to retrieve it for my clean installs.

Probably the BIOS doesn't display it (possible hidden menu's...) and you might try all boot prompts F1 to F12 for extra options.
The Recovery partition the manufacturer put on your disk drive has to contain the OEM key somewhere but I don't know where.

These are just some suggestions where to look, if the key is saved as most believe, there has to be a way to retrieve it. The vbs-script shows the currently installed version's key indeed.

I have TechNet keys so its no big deal for me. My Windows 8.0 TechNet install media reads it OK, but the TechNet 8.1 ISO does not. I've been though all the BIOS menu's and didn't see it listed. The factory recovery partition is long gone, that's an image file anyway. Without my TechNet key I would have been in a pickle that's for sure.

 

[SIW2]

Get it with this: View attachment 27558

 

[waltc]

I'm also a bit confused...Apps have not in my experience differed in origin when updating, AFAIK...

.. I think perhaps Waltc may be referring to..

Refresh your PC without affecting your files

• The apps that came with your PC or you installed from Windows Store will be reinstalled, but any apps you installed from other websites and DVDs will be removed. Windows puts a list of the removed apps on your desktop after refreshing your PC.

Bingo.... (I gave you fair warning...the gray cells are dying off at a prodigious rate...)

First, I forgot the the fact that Win8 doesn't like doing upgrades from DVD boots--as in I booted to the burned install DVD, selected the recommended "upgrade" install option--and then the program tells me, "Did you think we were *really* going to let you upgrade from here? Well, we aren't--reboot and run the upgrade from your Win8 boot, 'kay?"

Yeah, that was nice. ( Next, I get "refresh" language confused with "upgrade" language--although I certainly do think that Microsoft should be consistent when it says, "apps," don't you? When upgrading within 8.0 "apps" apparently means "all of the programs installed on your system", but when doing a "refresh" suddenly "apps" means "only those programs installed via the Microsoft store."

Thanks, Superfly. Tell the truth, Microsoft has done and said so many contradictory things this year--2013 has to be a record for Microsoft misstatements, turn-arounds, and bloopers. It's a wonder any of us has a decent handle on things, anymore, because it doesn't appear that Microsoft does.

I mean--just look at this situation...First Microsoft says, "Were doing 8.1 RTM beginning today but we aren't releasing to the public/developer community until October 18 (or thereabouts)." Predictably, the RTM is leaked and Microsoft goes ahead and releases to the public/developer, anyway. Then there's the whole "We aren't releasing an iso to consumers" Microsoft-employee blog, which seems like an incredible statement since 8.1 will be replacing 8.0 on retail shelves very soon (as we have already discussed.)

This entire year, Microsoft announcements--then retractions--have often sounded like they were coming from people who had never been a part of a Windows release before and for whom the whole thing was a brand-new experience. But the fact is that many of those people responsible for making the bad decisions this year had been at Microsoft for years--and *should* have known better (Mattrick and the xBone fiasco, for instance.) Weird & strange times, no doubt about it.

 

[theog]

If I find time later, I will test with the Retail option, may be the OEM manufacturer's will work the same.

http://www.eightforums.com/installa...retail-windows-8-1-windows-8-product-key.html

 

[alphanumeric]

Get it with this: View attachment 27558

You wouldn't happen to know where to look once you launch that utility?

 

[SIW2]

ACPI Table > MSDM tab. Product key is at the bottom.

 

[alphanumeric]

Thinking about this a bit more. May be it does read the embedded code but because its a Windows 8.0 code it ignores it? It's looking for an 8.1 code on a full install. Just for fun I did try entering one of my TechNet Windows 8.0 product codes and it wouldn't except that. I didn't get anywhere until I entered an actual 8.1 product code.

 

[alphanumeric]

ACPI Table > MSDM tab. Product key is at the bottom.

Thank you, that would appear to be it. :thumb:

 

[Hopachi]

ACPI Table > MSDM tab. Product key is at the bottom.

Thank you, that would appear to be it. :thumb:

Good finding!

I thought about RWEverything but the portable one mentioned uses the same options.

Thanks SIW2 for the help.

 

[Superfly]

Hi guys, thanx for the info.. was just wondering..

If you use a pid.txt with the default installation key, it should skip that initial request for a key, but will it still then require manual input of your OEM key from the bios ie. setup does not grab it like a it would for an original edition install and overwrite the initial key - so that all one would need to do is click 'activate now' or something?

If not, to automate one would then have to have a setupcomplete script to -upk and -ipk (with correct OEM key) and activate -ato?