Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

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

x86 file version from that site:

md5 = d597866e93bc8f80ecca234c4e9ce5a2

File version on extractor says: 6.0.6001.17028

I'm guessing it's RC Refresh build.

File a Bug Report

Oh that's right, you can't

HA HA HA HA HA HA HA HA HA

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]>

x86 file version from that site:

md5 = d597866e93bc8f80ecca234c4e9ce5a2

File version on extractor says: 6.0.6001.17028

I'm guessing it's RC Refresh build.

Even build 18000 says 17028 if you check the properties on the installer itself so it likely is RTM.

Why thank you so very much. Now I can have a nice day.

They are on there own, so why would you offer to help?

Because, we are a community. Here to not only give each other virtual wedgies but to maybe help with a suggestion; not just laughing at someones misfortune or problem.

OK, here's a question.

I have downloaded and installed the X86 SP1 instaler (everything ok).

The filename is: Windows6.0-KB936330-X86.exe

The filesize is: 455.562.200 bytes

The MD5 cheksum is: d597866e93bc8f80ecca234c4e9ce5a2 (as mentioned before in a previous post)

The build mentioned in registry is: 6001.longhorn_rtm.080118-1840

And finally the file's Digital Signature is 19 of January 2008.

Now, I have also downloaded two X64 SP1 installers (haven't tried them yet).

The first one is 761.740.600 bytes and signed on 19 of Jan also.

The second is 914.983.528 bytes and signed on 20 of Jan.

Both have the same filename: Windows6.0-KB936330-X64.exe

Could be the second that is the multilanquge pack? (because it's bigger), or it's the corrected version and not

the one that OEMs got? (still it's big though).

UPDATE: on Bink's site it says that "Windows Vista SP1 RC Refresh 2 = The RTM build" and that the one you can download

with the registry hack is SP1. :woot:

Edited by venejo
What's that supposed to mean?

Sorry if my post doesn't cut the mustard with you.

I was just trying to get an opinion on the validity of the article.

FYI: new = not noob necessarily

If that is all you have to say maybe you can post me a link to get a refund on my subscription?

Thank you to anybody else who would have an opinion.

ALERT: stand back, sense of humour failure detected :shiftyninja:

I've heard SP1 can't be slipstreamed and only SP2 will be.

What is the cleanest way to install Vista with SP2, then? Surely not installing Vista then installing SP2 on top of it? :s

I've heard SP1 can't be slipstreamed and only SP2 will be.

What is the cleanest way to install Vista with SP2, then? Surely not installing Vista then installing SP2 on top of it? :s

You can download a slipstreamed SP1 ISO.

Microsoft themselves must of done it?

I'm sure they will issue out SP1 discs as well at somepoint?

Of course as an end user it's also possible to go through a reverse integration process - http://www.winbeta.org/comments.php?catid=1&id=9536

However that is tricky/messy and I'd suggest just downloading the SP1 integrated ISO off the net.

I myself as I said earlier would only of installed SP1 if I could integrate it into the installation - For 2 reasons, 1 so I can use Vlite and the other as I don't like installing RTM and THEN SP1 on top... just doesn't feel "effecient" to me.

You can download a slipstreamed SP1 iso.

As in Microsoft themselves must of done it.

I'm sure they will issue out SP1 discs as well at somepoint?

Of course as an end user it's also possible to go through a reverse integration process - http://www.winbeta.org/comments.php?catid=1&id=9536

However that is tricky/messy and I'd suggest just downloading the SP1 integrated ISO off the net.

I'll do that when it's available (Y)

I'll do that when it's available (Y)

It's available right now :p (im running it)

But I get your drift, once MS themselves offer it as a download. Fair enough (Y)

I also read that slipstreaming *might* be possible via the updated AIK. I will be trying this out when I get home. I've been able to find a x86 integrated iso on the 'Net, but not a x64 integrated iso, which is mainly what I'm looking for.

Slipstreaming SP1 is not possible in any way, shape or form even with an updated AIK. vLite.net has more info in their second post on an alternative method to "slip" it.

Slipstreaming SP1 is not possible in any way, shape or form even with an updated AIK. vLite.net has more info in their second post on an alternative method to "slip" it.

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

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!