Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

Yeah, I did some more research. Evidently, you can use the updated AIK in the reverse integration method, but not slipstream.

Yea, the updated AIK's imagex can be used to capture the reverse integrated SP1 but it's not required, as in, you can also use the old RTM imagex and it'll work just fine.

Adrian Kingsley-Hughes which works at zdnet.com gave us the MD5 hashes of SP1:

Here:

32-bit (434MB): d597866e93bc8f80ecca234c4e9ce5a2

64-bit (726MB): 983308426e8ee7649f53b41f4e5c42d4

http://talkback.zdnet.com/5208-12354-0.htm...195&start=0

can someone confirms that this is the same MD5 hashes as RC1 ref. :D

haha 6001.longhorn_rtm.080118-1840 is not the RTM build!!

6001.18000.080126-2040 is the RTM build! see: http://www.aeroxp.org/board/index.php?show...&start=1035

The 1840 is the RC Refresh 2, distributed to testers using an update trick.

So whats the final sp1? 1840 or 2040?

Vista SP1 has been sent to manufacturers on disc and checks out at 1840.

That is where the full SP1 integrated ISOs that are on the net have come from.

Wow, you're totally useless and so is your post. :crazy:

Anyway, Daeron Tin?viel>, perhaps this Microsoft KB Article can help you:

You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services.[/b]>

thkz, try that didnt work

Do you need any hotfixes installed prior to installing the standalone EXE of SP1 like you did with the WU hack?

i installed SP1 with the EXE without installing any prior updates on a fresh install of vista ultimate, and i have yet to have any problems.

I don't know. What I posted was from my WU update history and that's what I downloaded from WU. It may be right or wrong but 17128 sounded familar to me so I checked.

Is there a CRC of a known good copy we can check this against? Or has someone tested this download?

Downloaded SP1 x86 from Sayuri yesterday, installed today - everything equals to information posted on Paul's Vista SP1 RTM page @ winsupersite.com; and file's MD5 hash exactly matches the ZDNet info.

Downloaded SP1 x86 from Sayuri yesterday, installed today - everything equals to information posted on Paul's Vista SP1 RTM page @ winsupersite.com; and file's MD5 hash exactly matches the ZDNet info.

What did the version number of the exe you installed say under the file properties.

Then just to clarify if the MD5 hash matchs d597866e93bc8f80ecca234c4e9ce5a2 but the build number on the exe says 6.0.6001.17028 that its actually the RTM and is safe to install?

Correct, the properties on the installer package file itself says 17028 but it is 18000 when installed.

Well just got done installing it. took about 30 to 40 mins

Installed the one that said .1728 but the m5 has matched and the current version inside the registry says "6001.18000.x86fre.longhorn_rtm.080118-1840"

Vista at lease to me feels much snappier. Just don't forget that if you patched your UXtheme.dll file that your custom theme will go POOF!

The Audio studding that I experienced before is better but not completely resolved. it is better though.

Network Transfer rates from my XP machine (media center) to this Vista machine is about 11 megs per second.

Like others have said the whole "Calculating time" is gone completely for single files"

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

    • No registered users viewing this page.
  • Posts

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • 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.
  • 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!