Anticipating Windows 10 RTM - would It Be Build 10400 or Build 10800?

By FaiKee
in The Fast Ring (Insider Previews)

 Share

Recommended Posts

Veteran

FaiKee

Posted
  • Author
Posted

Something I heard about win7 upgrade:

 

- must be done thru GWX, no other channel.
- there will be "a series of steps", I have no idea on the details.
- if it's Loader activated, forget about it.
- if it's BIOS mod, good luck (you'll need lots of it :laugh: )

  • vipanonymous
  • Like 1
Mentor

MikeM97

Posted
Posted

Something I heard about win7 upgrade:

 

- must be done thru GWX, no other channel.

- there will be "a series of steps", I have no idea on the details.

- if it's Loader activated, forget about it.

- if it's BIOS mod, good luck (you'll need lots of it :laugh: )

Sounds like a huge pack of rumors and nothing more.

I go with Xen here.

Veteran

FaiKee

Posted
  • Author
Posted

Well you can't do GWX through a Bootable USB install, so there's nothing to see about that. It will boot, and present you with the Custom or Upgrade choice window as usual.

Firstly, if you try upgrade from win7 directly to win10 with the win10ISO(or USB), I don't know if it could be done, you could try when the RTM image comes out.

 

Most importantly, even if it could be done, you couldn't activate the win10, it won't accept win7 keys, if you wish to get the free upgrade from win7 to win10, it has to be done thru GWX. :)

Grand Master

xendrome

Posted
Posted

Firstly, if you try upgrade from win7 directly to win10 with the win10ISO(or USB), I don't know if it could be done, you could try when the RTM image comes out.

 

Most importantly, even if it could be done, you couldn't activate the win10, it won't accept win7 keys, if you wish to get the free upgrade from win7 to win10, it has to be done thru GWX. :)

 

Why would you use a Windows 7 key on a retail copy of Windows 10? It comes with it's own key. And see below.

 

win10upgradematrix-100574156-large.jpg

Veteran

FaiKee

Posted
  • Author
Posted

Why would you use a Windows 7 key on a retail copy of Windows 10? It comes with it's own key. And see below.

 

win10upgradematrix-100574156-large.jpg

I was talking about the win7 free upgrade to win10, if you have your own win10 key, then it has nothing to do with the win7 free upgrade.

Grand Master

PGHammer

Posted
Posted

Something I heard about win7 upgrade:

 

- must be done thru GWX, no other channel.

- there will be "a series of steps", I have no idea on the details.

- if it's Loader activated, forget about it.

- if it's BIOS mod, good luck (you'll need lots of it :laugh: )

Not necessarily (in terms of BIOS mods) - there are still OEM BIOS images (complete with OEM keys baked in for Windows 7) out on the Internet - ready to be flashed using existing BIOS flashing tools.  The same process has been reverse-engineered for later versions of Windows, and even for UEFI BIOSes.  (It's even been applied to Apple OSes - that is, in a nutshell dump, how OS loaders for "Hacks" work.)

 

It's not rocket science.

Grand Master

xendrome

Posted
Posted

I was talking about the win7 free upgrade to win10, if you have your own win10 key, then it has nothing to do with the win7 free upgrade.

 

Well I was just going off what you said in your OP

Something I heard about win7 upgrade:
That's all. It wasn't specific to the Free upgrade.
Grand Master

xendrome

Posted
Posted

LOL, what a f**king mess.

:laugh:

MU7P4AM.jpg

 

Well since it's not complete and none of the builds are being sent through escrow this isn't even something they are doing at the moment, you've got some bad info TBH.

 

I wouldn't expect to see escrow builds and sign-off until probably the 9th through the 14th of July at the latest.

Veteran

FaiKee

Posted
  • Author
Posted

Well since it's not complete and none of the builds are being sent through escrow this isn't even something they are doing at the moment, you've got some bad info TBH.

 

I wouldn't expect to see escrow builds and sign-off until probably the 9th through the 14th of July at the latest.

I presume your argument is based on the incomplete and out-dated lists of Buildfeed? :)

 

jsHN1L6.jpg

Grand Master

Chris123NT

Posted
Posted

I presume your argument is based on the incomplete and out-dated lists of Buildfeed? :)

 

jsHN1L6.jpg

Looks to me like it's your info that is incomplete.  There's no lab names in those build strings....

 

And also buildfeed works by logging the windows update service for builds, obviously not every build is pushed to WU, even internally.

Veteran

FaiKee

Posted
  • Author
Posted

Nope, it's based on knowning how MS processes their builds and steps to RTM since going back forever.

 

Then I admire your knowledge, Sir. :)

Looks to me like it's your info that is incomplete.  There's no lab names in those build strings....

 

And also buildfeed works by logging the windows update service for builds, obviously not every build is pushed to WU, even internally.

I didn't say my info is complete, Chris, guess nobody could say that. We were just hearing and telling bits of things, I believe that's what everybody has been doing in forums and in blogs.  :)

 

btw, like you said, "not every build is pushed to WU, even internally"; could it happen that the escrow builds didn't appear in Buildfeed ....... or maybe @xendrome is actually the guy who has complete info of every build to know that there was no escrow build?

Veteran

FaiKee

Posted
  • Author
Posted

It was late last night when I replied in the last post, would like to add some small bits:

 

1. I respect hounsell and his hard work in BuildFeed, no intention to say bad things about it(like what canouna did), but it has its limitations like it couldn't be complete and it couldn't be always up-to-date, hope @chris123NT wouldn't misunderstand my intention in my previous post.

 

2. Win10 development is different, you couldn't use the "old ways" to look at it, previously we know the Windows build is in what stage as the build string would say things like beta, RC, escrow, etc., in win10, there was only a short period of fbl_awesome, where WinThreshold was transformed from Win8.2 to Win10, and features done in Project Windows 9(Windows Codename 9) was added to it, afterwards it was, and probably will be fbl_impressive all the way, the internal stages of beta, rc1, rc2, and probably escrow remain internal, it was not shown in build strings. :)

  • Jackaluichi
  • Like 1
Experienced

Jackaluichi

Posted
Posted

Man, people should stop stating RTM build has already been compiled. I see new builds from different branches being compiled every day. Are they aiming to a stable enough build to sign off and send to their partners? Sure, but that hasn't happened yet as far as we know.

Veteran

Studio384

Posted
Posted

It was late last night when I replied in the last post, would like to add some small bits:

 

1. I respect hounsell and his hard work in BuildFeed, no intention to say bad things about it(like what canouna did), but it has its limitations like it couldn't be complete and it couldn't be always up-to-date, hope @chris123NT wouldn't misunderstand my intention in my previous post.

 

2. Win10 development is different, you couldn't use the "old ways" to look at it, previously we know the Windows build is in what stage as the build string would say things like beta, RC, escrow, etc., in win10, there was only a short period of fbl_awesome, where WinThreshold was transformed from Win8.2 to Win10, and features done in Project Windows 9(Windows Codename 9) was added to it, afterwards it was, and probably will be fbl_impressive all the way, the internal stages of beta, rc1, rc2, and probably escrow remain internal, it was not shown in build strings. :)

 

So you're saying that Buildfeed has incomplete information because they don't show the escrow builds, but yet you yourself state that Microsoft can't decide which build to make escrow. If Microsoft doesn't know it, how should Buildfeed?

Veteran

FaiKee

Posted
  • Author
Posted

So you're saying that Buildfeed has incomplete information because they don't show the escrow builds, but yet you yourself state that Microsoft can't decide which build to make escrow. If Microsoft doesn't know it, how should Buildfeed?

Nope, I didn't say it, as @Chri123NT already said : "buildfeed works by logging the windows update service for builds, obviously not every build is pushed to WU, even internally", Also, escrow and sign-off candidate are different. :)

This topic is now closed to further replies.
 Share
Go to topic listing