Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

I just got an email from one of Microsoft people in Norway. She said SP1 likely will hit MSDN in early march.

Which isn't really news, as we already knew mid March as the WU release date.

If that's true though, and MSDN is being set to that date as well, then MS have to be doing some sort of build changes....

Sorry Lenin, just corrected that post, was sidetracked :)

Edited by Raa
Which isn't really news, as we already knew mid March as the WU release date.

If that's true though, and MSDN are being pushed back, then MS have to be doing some sort of build changes....

MSDN pushed back from what date?

Post your source!

It is NOT the final. The final has not been released. End of story.

While the code *has* gone gold, it won't be released from *shipping* until March 20th (per announcement from MS) due ot issues with certain drivers from certain companies (for some reason, the problematical driver manufacturers have not been named or leaked). Oddly enough, I'm running the last public version of Vista SP1 (RC Refresh) and I'm having no such issues with it or drivers I'm using with it.

i've been lurking on this thread here since feb 3rd. i dont understand how come some of you spend so much time speculating about things that have been made clear. just read what freaking MS said:

SP1 is done and it was released to OEMs (RTM) on the 4th. 99.9% of the code will remain the same as the RTW (release to web, consumer release). it has been released as is to OEMs as is because all of the OEMs can know if the 0.1% will affect them, and most importantly they can fix the problem if it arises . these issues, BTW, are related to some drivers breaking after SP1 is installed, which can be fixed simply by reinstalling the driver.

consumers, for the most part (obviously not the folks here) would have problems with those drivers breaking, so in order to ensure that as many consumers as possible will have a smooth experience, they wont let them grab a hold of sp1 until that 0.1% has been corrected.

even IF the code was 100% ok, they might have still done it the same way because they want sp1 to be available for download on the same day that the very first new pc running sp1 hits the shelves of your nearest circuit city. would you have done it this way if you were billy? no. is it understandable? completely.

in a few words, RC (refresh 2) IS the final SP1, as it was correctly speculated on technet in late january. if that release is working for you, it means that the 0.1% involves drivers which your system does not use, and therefore, in your case, that version is effectively the same as the RTW. what will the version # be? i have no clue, but it will probably not be the january 28 18:40 build.

want the final sp1? install refresh 2, any drivers break, reinstall those drivers, you're done. then go back to doing something useful.

EDIT: basically i'm just putting into more words what PGHammer said above.

Greetings, all.

I've been lurking around here for quite some time.

After using the registry hack posted earlier in the thread, I downloaded the "Release Candidate 1" version of Vista SP1 off of Windows Update. However, unlike the previous test versions I had installed this version did not contain a version number for this service pack, or an expiration date, as shown in the attached screencap.

I did not install Refresh 2 when it came out, so I didn't actually catch whether or not it had a version number/expiration attached to it (though I assume it did). So I'm wondering if, while everything on WU is still labelled RC1, whether Microsoft has quietly slipped the RTM code in place behind it.

Not sure. At any rate, it installed fine and if, for some reason, this isn't the RTM, then I simply re-install it in a month's time.

Just thought I'd make this observation.

post-146089-1202317452_thumb.jpg

:D No. But I'm angry at Microsoft, they just can't seem to stop monkeying about with Vista. If the final slipstreamed iso isn't on connect in the next 24 hours. I'm abandoning this ship.

no dont do that! without you microsoft will collapse!

While the code *has* gone gold, it won't be released from *shipping* until March 20th (per announcement from MS) due ot issues with certain drivers from certain companies (for some reason, the problematical driver manufacturers have not been named or leaked). Oddly enough, I'm running the last public version of Vista SP1 (RC Refresh) and I'm having no such issues with it or drivers I'm using with it.

could be nvidia

i dunno but i had major probs with my network card with 18000

well, winsupersite is a good enough source of windows info but imho unless the iso shows up on msdn its not 100% confirmed.. just what I think

I've heard in another group that the copy of sp1 that was from january is indeed the rtm

"Windows Vista SP1 build 18000 is indeed the RTM build. We were hoping build

18000 we released to you (WU only) was the final build and as it happens we

didn't have to break the glass, the build didn't change at all from the time

we released it to you and our final sign-off on Monday morning this week.

What you got is what we're all running our Vista machines here internally -

we definitely RTM'd :)

You've probably all read that we are targeting mid-March to release SP1

standalone on the download center and push SP1 out via WU. We've seen a lot

of requests from our tech beta for bits on Connect before hand we're still

trying to get approval for that, so stay tuned.

We apologize for the confusion over the final build - build 18000, Vista SP1

RTM.

Regards,

Jeff"

Greetings, all.

I've been lurking around here for quite some time.

After using the registry hack posted earlier in the thread, I downloaded the "Release Candidate 1" version of Vista SP1 off of Windows Update. However, unlike the previous test versions I had installed this version did not contain a version number for this service pack, or an expiration date, as shown in the attached screencap.

I did not install Refresh 2 when it came out, so I didn't actually catch whether or not it had a version number/expiration attached to it (though I assume it did). So I'm wondering if, while everything on WU is still labelled RC1, whether Microsoft has quietly slipped the RTM code in place behind it.

Not sure. At any rate, it installed fine and if, for some reason, this isn't the RTM, then I simply re-install it in a month's time.

Just thought I'd make this observation.

That is the RTM bits. Even though it is labeled as RC1 something on Windows Update it is RTM. You have the final version. Enjoy!

I've read reports of Vista SP1 discs (holographic) being sent out already and SP1 RTM is the build thats been on the web the last few days.

I took the 32BIT SP1 RTM full iso, Vlited it and installed and it's working great! :D

Glad the integrated package exists as I refuse to install Vista with all the bloat. My install DVD is down to around 600MB from a couple of GB.

I've read reports of Vista SP1 discs (holographic) being sent out already and SP1 RTM is the build thats been on the web the last few days.

I took the 32BIT SP1 RTM full iso, Vlited it and installed and it's working great! :D

Glad the integrated package exists as I refuse to install Vista with all the bloat. My install DVD is down to around 600MB from a couple of GB.

Yeh same, I also never install Vista with all of the bloat.

I've seen a definite performance increase on my laptop with single processor, it seems everything is much more responsive than what it used to be.

off-topic question

does windows 2008 server have Directx10? Does it have superfetch?

anyone know if their will ever be a pro version

Win2k8 server I believe doesn't have DirectX10 as its not meant for gaming but not 100% sure if it has it or not, doesn't make sense to me if it did tho. As for superfetech no idea if it does.

there's no switch to install the service pack without an uninstall method...

Does anyone know how to install it without creating an uninstall folder with a bunch of crap in it?

thanks!

you can clean up afterwards by running

vsp1cln.exe

I've heard in another group that the copy of sp1 that was from january is indeed the rtm

"Windows Vista SP1 build 18000 is indeed the RTM build. We were hoping build

18000 we released to you (WU only) was the final build and as it happens we

didn't have to break the glass, the build didn't change at all from the time

we released it to you and our final sign-off on Monday morning this week.

What you got is what we're all running our Vista machines here internally -

we definitely RTM'd :)

You've probably all read that we are targeting mid-March to release SP1

standalone on the download center and push SP1 out via WU. We've seen a lot

of requests from our tech beta for bits on Connect before hand we're still

trying to get approval for that, so stay tuned.

We apologize for the confusion over the final build - build 18000, Vista SP1

RTM.

Regards,

Jeff"

This was posted on the Connect newsgroups for the SP1 beta program and is 100% correct. Rest assured: Windows Vista SP1 RC Refresh 2 is indeed the RTM build.

off-topic question

does windows 2008 server have Directx10? Does it have superfetch?

anyone know if their will ever be a pro version

It should have DX10.1 if you install the desktop experience.

Superfetch should be on by default, but tuned to a server environment.

No, there will not be a Windows 2008 Pro, Vista SP1 is Windows 2008 Pro. (Turn off the themes service in Vista, it will look like Windows 2008)

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

    • No registered users viewing this page.
  • Posts

    • Yup, that's a doozy right there 😄
    • It's a bundle of tools created by a variety of people, so things can go wrong sometimes. It's a great addition to Windows, and I use a lot of the tools on a daily basis. Also, it's still a 0.**** release so quick updates are to be expected 😉
    • Oh, I did. And it's even worse than I was hoping! Besides a lot of techno-babble jargon (yes I understand 100% of it but it's still all just techno-babble) there's 2 key points that make me super-weary about even considering testing this out. -- By default, after installation, a relay is automatically set up, so you do not need to care about that. * Non-chatmail apps use email servers as a long-term message archive while chatmail clients use email servers for ephemeral instant message relay. * Supporting the full variety of classic email setups would require considerable development and maintenance efforts, and complicate making chatmail-based messaging more resilient, reliable and fast. -- Basically, the end-user device is the 'server' (relay) so there is NO ARCHIVING whatsoever because every message is necessarily ephemeral. Great for techno-paranoia (and for illicit activities preferring no tracks to cover) but terrible for everybody else. It's also ironically contradictory to engineering principles of redundancies besides the transport layers due to the explicit absence of any persistent storage. Instead of 'classic email address' retaining multi-GB messaging archives on its server, now every device must retain 100% of those storage demands. (Email messages were originally meant to be short correspondences, not the multi-MB attachments boondoggle that now exists with unlimited spam engines flooding every potential recipient.) Any device swap or reset (or loss) makes the entire message history go bye-bye forever... lest there's an off-device auto-archival "relay" mechanism that's really a separate server that holds onto all transported messages (an email server) that utilizes 'chatmail email address' identities (like an email server) and its own persistent storage archive (like an email server). But... this solution is hoping to exist alongside real-world email address identities (based on the email server relay pathway) but simply render messages in chat thread format in an ephemeral manner (with contents being encrypted, and messages auto-expiring) ... In the end, it's a chat app/experience for the Web3/P2P-at-all-costs zealots. (I have accts on all sorts of federated web3 services so I understand the technical and non-technical alike.) For any practical users, however, it's just another service to download/install, register, cross-share id cards/qr codes, but know that there's no history/archive whatsoever (by design) so no account/message recovery whatsoever... update the device, install a bummed update patch, or dare upgrade your device... all history, poof, gone. Ya gotta start everything over again like they're a brand new person.
    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!