Windows 7 RTM Discussion


Recommended Posts

I say, most of the error occurred was by user error. Like they didn't check what can be trust and what can't, then they download an infected/corrupted ISO, or crack it with illegal activators. They blame for the errors. The same as someone enters some illegal porn web and his pc gets infected by virus, then he blames his OS that it lacks securities.

Yes, we don't know if WZor's one is clean. But if you read in that 'thread' of your, there's a confirmation that it doesn't occur on theirs(assuming Chris123NT's using WZor's). Or at least it doesn't occur on mine.

And if you read that post carefully, zachdms never mentioned that 16835 we're using aren't real. He's saying that grabbing random things off the net causes the problem(probably because of infected/corrupted ISO or activations as I mention above)

Of course he wouldn't know because he wouldn't have actually downloaded it himself. :rolleyes:

And I didn't say that the ISO Wzor provided was infected, merely that there's reports that it's using the 16385 directories and the 16384 boot data for the ISO. Hence, wait for the official one from Microsoft next week and you'll see that the file hashes are most likely different.

PS. Yay @ the kind of people this stuff brings to Neowin. "footgay" - honestly? :|

Link to comment
Share on other sites

Of course he wouldn't know because he wouldn't have actually downloaded it himself. :rolleyes:

And I didn't say that the ISO Wzor provided was infected, merely that there's reports that it's using the 16385 directories and the 16384 boot data for the ISO. Hence, wait for the official one from Microsoft next week and you'll see that the file hashes are most likely different.

PS. Yay @ the kind of people this stuff brings to Neowin. "footgay" - honestly? :|

Wzor iso is not using a boot sector from 16384. Furthermore, the iso itself was compiled inside microsoft, just not on the regular iso building machine (that's why iso hashes won't match with the "proper" one). Stop spreading baseless rumors.

Link to comment
Share on other sites

There's at least two reports of people having issues with the leaked 16385 build that don't occur with the official Microsoft build. It'd be wise for people who installed it to re-install once the ISOs are made available from Microsoft (with official hashes).

I have leaked 16385 and don't have that problem. Last night i removed games (windows turnoff feature).

Link to comment
Share on other sites

Wzor iso is not using a boot sector from 16384. Furthermore, the iso itself was compiled inside microsoft, just not on the regular iso building machine (that's why iso hashes won't match with the "proper" one). Stop spreading baseless rumors.

I must get one of those "iso building machines" for the office someday. Seriously though, some people, maybe not yourself, are under the impression that the leaked ISOs they're downloading and installing are exactly the same as what's going to be released by Microsoft next week. So given the high likelyhood that they're not, it might save some people who actually care that they have official media, some time otherwise wasted downloading and re-installing the final version.

It's like buying a car engine from a shady dealer when you don't know what a genuine real engine looks like.

Link to comment
Share on other sites

I must get one of those "iso building machines" for the office someday. Seriously though, some people, maybe not yourself, are under the impression that the leaked ISOs they're downloading and installing are exactly the same as what's going to be released by Microsoft next week. So given the high likelyhood that they're not, it might save some people who actually care that they have official media, some time otherwise wasted downloading and re-installing the final version.

As I said above, it will not be the same iso, hashes won't match, but the iso from wzor is still a pure 16385 iso without 16384 boot sector (unlike the "home made" isos that were made from the chinese leak). When the 16385 iso was distributed to microsoft partners (prior to rtm signing), the only form it was available in was loose files and folders. No iso or vhd of 16385 was made then. Wzor got their contact inside microsoft (that has been feeding them info and builds all this time) to put together an iso for them. End of story.

Link to comment
Share on other sites

Of course he wouldn't know because he wouldn't have actually downloaded it himself. :rolleyes:

And I didn't say that the ISO Wzor provided was infected, merely that there's reports that it's using the 16385 directories and the 16384 boot data for the ISO. Hence, wait for the official one from Microsoft next week and you'll see that the file hashes are most likely different.

PS. Yay @ the kind of people this stuff brings to Neowin. "footgay" - honestly? :|

Of course it will be different, even with the exact same files inside. The ISOs' hash always change. That's why people suggest on checking install.wim hash if not all files in ISOs.

And what's on about my name, honestly?

Link to comment
Share on other sites

As I said above, it will not be the same iso, hashes won't match, but the iso from wzor is still a pure 16385 iso without 16384 boot sector (unlike the "home made" isos that were made from the chinese leak). When the 16385 iso was distributed to microsoft partners (prior to rtm signing), the only form it was available in was loose files and folders. No iso or vhd of 16385 was made then. Wzor got their contact inside microsoft (that has been feeding them info and builds all this time) to put together an iso for them. End of story.

If you say so...

Link to comment
Share on other sites

I recall Wzor (which I would personally put more trust in) released their version after this leak by, uh, *looks* "segobi" for a censored forum here on Neowin, that leaked during this frenzy when everyone had to have the RTM preferrably yesterday. I believe this is based on a hacked chinese leak some are talking about, and that should ring enough warning bells alone. Both releases are "everywhere" online now.

I also believe in what vask is saying here. Wzor seem to have some very "good" (from a warez group's perspective) sources inside Microsoft, judging by their history. If I were to choose myself, I'd never pick a re-engineered chinese release.

Link to comment
Share on other sites

August 6th is the latest date thrown in for official release of the RTM..

Following all of the recent reports announcing the release date of Windows 7 RTM Microsoft CEO Steve Ballmer has now announced that the RTM is complete. According to reports Steve signed a gold Windows 7 RTM DVD live at a sales event in Atlanta.

According to the report on InformationWeek developers with MSDN and TechNet subscriptions will be able to download the RTM on August 6th, this is also the case for independent software and hardware vendors.

Consumers will be able to get hold of the software as of October 22nd, whereas Microsoft Partner Program Gold/Certified members will receive the Windows 7 RTM software on August 16th, Microsoft Action Pack subscribers will have to wait another week as they can download the RTM on August 23rd.

Source

Link to comment
Share on other sites

Of course it will be different, even with the exact same files inside. The ISOs' hash always change. That's why people suggest on checking install.wim hash if not all files in ISOs.

And what's on about my name, honestly?

Even install.wim will change, cause the original leaked 16385 had the actual compilation dates for the files inside (not all are the same). The retail 16385 install.wim will have those dates all set to one and the same date/time stamp. But the actual binaries will never change.

Edited by salamanca
Link to comment
Share on other sites

Just to be on the safe side, i'm going to install Windows XP, activate it, then upgrade+clean install 7 and rearm until I get my upgrade key in OCT.

Link to comment
Share on other sites

I purchased the Professional version. Is there any safe way that I can get one of these official leaks and use it until I get my key in October? I really don't want to do another reinstall.

Link to comment
Share on other sites

deihmos, the ultimate version will probably let you choose to install the pro version, you have 30day to trial it. You can use slmgr -rearm trick to allow you to test it for 3 months then activate with your serial once your disc arrives.

Link to comment
Share on other sites

Even install.wim will change, cause the original leaked 16385 had the actual compilation dates for the files inside (not all are the same). The retail 16385 install.wim will have those dates all set to one and the same date/time stamp. But the actual binaries will never change.

You are mistaken. The official ISO leak with hashes verified by MS contains an install.wim file the hash of which matches hashes from the 16385 leaks.

This indicates that the dates have not in fact changed.

Link to comment
Share on other sites

Official ISOs have indeed been leaked. Didn't take long ! At least it's the last one. We won't be hearing about Win7 leaks anymore, hurray !

Yes, the days of Win7 leaks are definitely over.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.