Vista SP1's Slipstreaming Mess!

By Avi
in Back Page News

 Share

Recommended Posts

Mentor

Avi

Posted
Posted
"Can I slipstream Windows Vista SP1 into an existing install image?"

Nope. Well, not directly, anyway.

"Um.. but when I get SP1, I want to upgrade my deployable .WIM images with the new bits. I can't do that in an offline way like I can with other updates?"

Sorry. No.

"Are you going to tell me why?"

Absolutely! You don't think I would have opened up this nasty can of worms without giving you a good explanation, did you?

"Well..."

Okay. So here's the deal. And those of you who have experienced the SP1 installation have experienced this as well. When you do the SP1 installation, even if it's from Windows Update (when available), you're going to see your machine shutdown and restart on it's own several times. That's to be expected. See, there's this important part of the OS known as the "servicing layer" in Windows Vista and Windows Server 2008. This is the part of the OS that allows for easy update installation with minimal disruptions, allows for an update to be applied to an offline captured image that's within a .wim file, among other things. Well... let's say that that servicing layer ALSO needed to be updated? What then?

"Oh.. I get it. You can't update the thing that makes the updates happen smoothly, because the thing that makes updates go smoothly is itself being updated!"

Bingo. You got it. So hopefully the news that you can't just do an offline upgrade to an image .WIM file won't be too tragic.

"So.. what do I do instead?"

You are going to have to install your image to a machine. Install the Service Pack. Then re-capture the image.

"Simple!"

Not so simple. There are additional steps that involve some cleanup once you've sysprepped your newly updated SP1 machine. Detailed steps are available in the new WAIK documentation.

"Won't I lose a valuable re-arm to my image when I apply the service pack this way?"

No. SP1 grants you an additional re-arm. We don't want you to be penalized for having to generalize a system that additional time.

"Wait... there's a new WAIK?"

If you're using the WAIK (Windows Automated Installation Kit), you will definitely want to get the new version that has support for both the original Vista as well as the new servicing layer that's in both Windows Vista SP1 and Windows Server 2008.

Of course, the easiest way to do this all would be to get a copy pre-slipstreamed SP1 version of Windows Vista from Microsoft when it becomes available, and start with that as your new installation base. If you're not doing any other custom image management, that's definitely the easiest solution. Just add it to your own Microsoft Deployment workbench or use it to build your new images from there.

See Source

On other notes, Microsoft made its own slipstreamed image available to its MVLS partners!

Link to comment
https://www.neowin.net/forum/topic/618945-vista-sp1s-slipstreaming-mess/
Share on other sites
Grand Master

HawkMan

Posted
Posted
So we cant install SP1 until Vista is installed :(

umm well when SP1 is releaed MS i also releaseing new install media with SP1, these are the ones that will be sold to utomers after SP1 is released as well.

This seems more to relate to making your own slipstream media, without haign the updated disk yourself, but from your own, but it also explains how to make it sort of from wht I can gather so I don't see the problem.

Grand Master

+Audioboxer Subscriber²

Posted
  • Subscriber²
Posted

Images with SP1 integrated exist.

Just ignore MS and get elsewhere - Not great on MS' part, but it solves your issue as an end user.

(the images have come from SP1 discs MS sent to manufacturers, they aren't some user mash ups)

Experienced

Swiftie

Posted
Posted
Images with SP1 integrated exist.

Just ignore MS and get elsewhere - Not great on MS' part, but it solves your issue as an end user.

(the images have come from SP1 discs MS sent to manufacturers, they aren't some user mash ups)

This surely goes againt what you just said doesnt it?

mbn7eg.png

Veteran

Phemo

Posted
Posted
This surely goes againt what you just said doesnt it?

Looks like he's agreeing to me? That shot shows MS have released SP1 integrated ISOs themselves, and Audioboxer just said MS SP1 integrated ISOs are out there, so I'm not sure what you mean?

Edit: Oh I see what you mean. Yes so they are available from MS, but not to everyone.

Grand Master

Colin-uk Veteran

Posted
  • Veteran
Posted

slipstreaming is generally for advanced users, I dont think the average joe will slipstream his vista install.

and its not like thier even stopping you from doing it at all or installing updates. its not exactly hard to run a .exe and click a few buttons after install now, is it.

plus, MS are releasing slipstreamed images to retail now anyway.

Contributor

rdxg0d

Posted
Posted

You ever think that microsoft made it difficult for a reason...mainly so ppl dont pirate it, or worse average idiots dont start trying to slipstream and clog up the tech support lines....besides the documentation is there on technet, and its in the WAIK, if you cant figure it out then you shouldnt be even attempting it....Microsoft does things for a reason....and as someone said in a previous post if you cant make a few clicks to install the service pack then your just lazy....

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine

      By LoneWolfSL · Posted

      Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By Primey_ · Posted

      The nerve of Google to sign this.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By s0nic69 · Posted

      I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By The Norwegian Drone Pilot · Posted

      It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more

      By David Uzondu · Posted

      JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.

  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later

  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!