Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

yea this has been leaked... now i wait for the xp sp3

Source? Confirmed final build?

Didn't think so.

And agreed, that Server 2008 post has nothing to do with this topic!

Torrentthief : Go post in the right thread :p Thanks for the info, nothing my email didn't already tell me (its on connect now)

Based on various responses this can be possible

6001.18000.080118-1840 ----> RC Refresh 2 (Mistakenly taken as RTM Build since it doesnt have time bomb and watermark)

6001.18000.080126-2040 ----> Possibly an Escrow Build (Build of which final testing of SP1 took place as previous one had some serious flaw... Still a very mysterious build)

6001.18000.080131-1830 ---->Supposedly The final build of Vista SP1

EDIT: Story takes new turn as microsoft have posted Automated Installation Kit (AIK) for Windows Vista SP1 which has build 6001.18000.080118-1840

http://www.microsoft.com/downloads/details...;DisplayLang=en

Edited by sanke1
Based on various responses this can be possible

6001.18000.080118-1840 ----> RC Refresh 2 (Mistakenly taken as RTM Build since it doesnt have time bomb and watermark)

6001.18000.080126-2040 ----> Possibly an Escrow Build (Build of which final testing of SP1 took place as previous one had some serious flaw... Still a very mysterious build)

6001.18000.080131-1830 ---->Supposedly The final build of Vista SP1

RTM Build is 6001.18000.080118-1840

You can be sure by looking at the build number of Windows AIK on the ms download center.

Windows AIK Build 6001.18000.080118-1840

Oops, the same time sanke1 :)

I've got a somewhat crazy idea here,

Why don't we all just wait until it appears on Connect, MS Download or MSDN/TechNet? I'm all for getting SP1 installed on every Vista box I take care of, heck I live for this kind of stuff. Being the earliest of early adopters definitely has its moments, but I'm not going to risk downloading and installing a build off of some warez site.

So the download on that Vista forum is the real deal? It shows "6001.longhorn_rtm.080118-1840" in the registry. It was posted on Friday so I thought it would be RTM.

I hope this is true as I have spent almost six hours installing it on my desktop and laptop :sleep:

So the download on that Vista forum is the real deal? It shows "6001.longhorn_rtm.080118-1840" in the registry. It was posted on Friday so I thought it would be RTM.

I hope this is true as I have spent almost six hours installing it on my desktop and laptop :sleep:

I dunno WHAT to believe. It seems half say "it's the old RC Refresh 2", while the other half say "it's the RTM". Guess the only way is to find out for yourself.

I'm gunna wait till it hits technet/msdn/connect and get ppl to find out the exact build number and number of bytes the .iso is and .exe is, not worth formatting and setting up vista sp1 to find out a few days later it isnt the rtm build.

The AIK kit build does NOT reflect the final build of Vista SP1.

It could be the same build number, or it might not be.

The ONLY fact we have right now is that Vista SP1 is RTM, but has NOT been released to web.

correct. that AIK Kit is just a kit to help you use sp1, im sure that would have been finished before vista itself. im thinking the 0131 build is the rtm or even newer as they said on friday it wasnt finished which was 1st feb (0201).

So just be patient and hang in there:) cant believe no-one from dell etc has leaked the build number or anything.

I'm gunna wait till it hits technet/msdn/connect and get ppl to find out the exact build number and number of bytes the .iso is and .exe is, not worth formatting and setting up vista sp1 to find out a few days later it isnt the rtm build.

NO

Having to much fun with this.

question: i see torrents with the full dvd(sp1 integrated) with build 6001.18000.080118-1840. i guess this is the real deal? since i have read somewhere that sp1 cant be slipstreamed, i would guess this is the real deal...right?

NO! It is NOT!

It has NOT been RELEASED TO WEB (Inc MSDN, Connect, etc.)

Any links or downloads are UNCONFIRMED at this time.

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

    • No registered users viewing this page.
  • Posts

    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
    • OK so SearXNG is a meta search engine that you can install locally or use via a public instance. It scrapes other search engines which you choose and then sorts the results. Not as complicated as multiple relays
  • 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
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!