Yes, SP1 integrated for All versions. From Wzor. Russsian: "Как мы говорили выше, компанией Microsoft собрано около 3000 дистрибутивов, и порядка 150-ти дистрибутивов из этой кучи с интегрированным пакетом обновлений возможно будет размещена в сети, это займет какое-то время, работа над этим идет."
Anyone confirm that usb3 works natively and blue tooth v3?,, don't have usb3 but I have blue tooth v3 and don't notice any difference.
On that x64 Enterprise VL slipstreamed leak, you will notice the very short EULA during install. If you delete the ei.cfg, you will get a different EULA
The enterprise install.wim has all other versions? I ask this because if you delete ei.cfg on ultimate (for example) the enterprise option won't be there during install.
I know. The reason for deleting the ei.cfg was to see which EULA would get pulled. With the ei.cfg, it loads up the EULA license rtf from \sources\license\en-us\oem\enterprise. Which is the extremely short EULA with the tag "EULAID:Win7SP1_RM.0_E_VL_en-us" When ei.cfg is missing, you get Win7SP1_RM.2_E_RTL_en-us
may sound noobish but, are enterprise and consumer installations on seperate discs? cause the one i have just has consumer ones. also TPB deleted me and my torrent anyway il keep seeding it for those who are leeching it
*sighs* This is why people should always go to the SOURCE instead of reading some idiotic news article. The source (i.e., the edit made to the TechNet article) simply denied that SP1 had been released to OEMs and said that the original post had "inaccuracies" (but did not specify what kind of inaccuracies). It NEVER denied that this was RTM; it simply refused to confirm it and refuted unspecified claims (from the very start, we knew that releasing stuff to OEMs on a Saturday was pretty obviously wrong, even without an official refutation). But then various "news" articles took this, disregarded the subtle nuances in the official line, and thus came up with interpretations (e.g., "not RTM") that were never expressed by Microsoft. On the same token, various "news" sites took a rogue Russian post on TechNet and somehow elevated that to an official announcement from Redmond. Always go to the source; people should know by now that messages are always distorted and important nuances lost when you play the game of telephone. For people who have doubts, I'll refer back to this post:
Regarding your 976902 post, one person DID make the servicingstack discovery before you mentioned it today, but I realize that this thread is too long to go through in its entirety. As a reminder, I brought it up in this thread a couple days ago by linking to the person who came up with it a couple days before the leak even occurred. On your first point, MS did deny that it was RTM in a briefing with Paul Thurrott. There's every reason to believe they weren't being truthful with him, but it did happen. The vr-zone article, oddly, basically drew the headline of their article from this fact without actually describing the source in the article. You're right that the edit of the Russian blog is hopelessly vague.
Well so much for SP1. I've just system restored to get rid of it. It has caused me nothing but trouble. Windows booting to a black screen after logon, over 10 issues in device manager. Not sure what to make of it but its not good that's for sure. To be honest, now I'm not even convinced I need SP1. My machine runs perfectly without it.
You have jumped the gun by assuming that this is not SP1. There is a lot of evidence to support the fact that it is the final release, such as the servicing stack using the same build string in KB976902. I installed SP1 on two machines. One machine had no issues, the other had problems - but it was related to KB976902, and not SP1 itself. After KB976902 was installed on the problematic machine (through Windows Update), the internet would not function unless I disabled and re-enabled the ethernet adapter in the device manager. Windows Update was also stuck in an infinite loop while checking for updates. After some investigation, I checked C:\WINDOWS\Logs\CBS\CBS.log, and it was constantly getting spammed with errors related to "ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE". I solved the problem by running the Windows 7, x64 version of the System Update Readiness Tool (KB947821), and SP1 installed with no further issues.
I'm not saying its not SP1 rtm , I've also installed that on update too. I'm just saying I question the quality of the SP.