Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

If it really did RTM today, it'll leak today or tomorrow.

I think there's some smoke and mirrors rubbish going on MajinDark, Microsoft tells us VistaSP1 is done. Then delays release until March. Seems to me like it's not really RTM at all.

...."Our beta testing identified an

issue with a small set of device drivers. These drivers do not

follow our guidelines for driver installation and as a result, some

beta participants who were using Windows Vista and updated to

Service Pack 1 reported issues with these devices. Because the

issue was with the way the drivers were installed and not the

drivers themselves, the solution was simply to reinstall the

drivers. While this worked fine for our more technical beta

testers, we want to deliver a better experience for customers as we

make the update broadly available."

Source: WindowsVistaBlog

That statement seems to be to say... 'We're not done yet, Vista SP1 isn't really Final.' :rofl:

Just can't get Vista right can they. Once again the release of Windows Vista is based on a shipping schedule not quality. (N)

Edited by 1Frothy

ok well that one that is from Vista forums is total junk and fake.

it's the old RC Refresh build.

Screenshot:

post-698-1202162467_thumb.jpg

http://winvistaforums.com/downloads/Window...B936330-X86.exe

that was downloaded from that link which is from the page earlier.

Digital sig: Saturday, January 19, 2008 8:40:35 AM

ok well that one that is from Vista forums is total junk and fake.

it's the old RC Refresh build.

Screenshot:

post-698-1202162467_thumb.jpg

http://winvistaforums.com/downloads/Window...B936330-X86.exe

that was downloaded from that link which is from the page earlier.

Thanks for testing it KoDeXeRo, I was going to check that download out. :/

I think this is funny, but true...

Is there a reason for the waiting time til mid-march?

When it's ready - release it.

When it's not ready - delay it.

I can't see really the benefit of an RTM Version of SP1 when I can't have it.

This release is making Vista SP1 look bad right out of the gates...

is this linky the SP1 of Vista??

Dont think so but the build name of that file for the automated installations is the same build that i am already running (see my other post).....

Does this mean the rtm really was leaked?

Is this the RTM build?

i assume you found and installed the same file that i did last week. that's also the same version mine reports.

yet the details/timestamp on the .exe i have are the same as the one that KoDeXeRo posted. :p

i assume you found and installed the same file that i did last week. that's also the same version mine reports.

yet the details/timestamp on the .exe i have are the same as the one that KoDeXeRo posted. :p

Then you have the wrong one!

post-109044-1202166895_thumb.jpg

Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008

No, it's the automated installation kit for SP1.

... and what exactly is an Automated Installation Kit as compared to the 'regular SP1?

ok well that one that is from Vista forums is total junk and fake.

it's the old RC Refresh build.

Screenshot:

post-698-1202162467_thumb.jpg

http://winvistaforums.com/downloads/Window...B936330-X86.exe

that was downloaded from that link which is from the page earlier.

Digital sig: Saturday, January 19, 2008 8:40:35 AM

yea but once unpacked its 6001.longhorn_rtm.080118-1840 and the unpacked setup files are build 6.0.6001.18000, so it's note fake.

If you think you have the final SP1, then do us a favor : forward your clock a year and tell us if you can still boot up.

What? Don't want to? But you SAID you had RTM!!

Yeah, didn't think so.

works just fine......... i dont see the problem u were expecting. the time bomb was removed from refresh two onwards.

Then you have the wrong one!

really? like i said, my file details match the one KoDeXeRo posted........ but once it's installed, it matches the build in your screenshot.....

ea5a9b45b98630fa10de4bc90667d505.jpg

Edited by marc2003
Then you have the wrong one!

Actually you're comparing two different files. spinstall.exe shows the 18000 version number, but the other poster has shown properties from the standalone installer which shows 17028 in the properties. The standalone installer I have here shows 17028 in properties, but when you launch the installer and check spinstall.exe in the temp files, it shows 18000 :) It's likely that 17028 is totally legit.

If you think you have the final SP1, then do us a favor : forward your clock a year and tell us if you can still boot up.

What? Don't want to? But you SAID you had RTM!!

Yeah, didn't think so.

The timebomb was removed from the last refresh, so if it's fake I bet they used the last refresh. So I don't see what that is going to prove.

really? like i said, my file details match the one KoDeXeRo posted........ but once it's installed, it matches the build in your screenshot.....

Yeah your right..... but why does the properties of the exe change? I huess ultimately we are all wasting our time here! It doesnt really matter what build we have... no amount of sitting here and speculating will change that we have to wait till march to really find out!

Actually you're comparing two different files. spinstall.exe shows the 18000 version number, but the other poster has shown properties from the standalone installer which shows 17028 in the properties. The standalone installer I have here shows 17028 in properties, but when you launch the installer and check spinstall.exe in the temp files, it shows 18000 :) It's likely that 17028 is totally legit.

do you think we can assume that because the leaked build matches the server 2008 build number exaclty we can assume we are using SP1 RTM?

do you think we can assume that because the leaked build matches the server 2008 build number exaclty we can assume we are using SP1 RTM?

loads of people have posted about this today as if it's a fact...... but with no source to back it up. i guess we'll just have to wait. :p

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

    • No registered users viewing this page.
  • Posts

    • Blast from the past.
    • Hello, Were you using a product or service from one of the companies affected by the Klue data breach?  See https://klue.com/blog/an-update-on-recent-klue-security-incident for the company's public statement.  That blog post does not list affected customer. From looking around at reports, I created this list: Gong HackerOne Huntress Insurity Jamf LastPass OneTrust Recorded Future ReliaQuest Salesforce Snyk Sprout Social Tanium It is likely there are other companies affected as well. Regards, Aryeh Goretsky  
    • SpaceX reportedly plans a Starlink mobile service for U.S. consumers by Karthik Mudaliar SpaceX reportedly wants to sell mobile phone plans directly to consumers in the United States as part of a wider expansion of Starlink. According to a report from the Financial Times, SpaceX president Gwynne Shotwell discussed the plan with investors during the company’s recent IPO roadshow. The company is also said to be considering building a terrestrial mobile network to complement Starlink’s satellite coverage. The plan is quite different from how Starlink currently operates in the U.S. mobile market. SpaceX already provides satellite connectivity for T-Mobile’s T-Satellite service, but T-Mobile remains responsible for the subscription, billing, and customer support. A Starlink-branded mobile service would give SpaceX control of the customer relationship instead. It could also turn the company from a partner of traditional mobile operators into a direct competitor. T-Mobile also began testing its Starlink-powered satellite service in early 2025. The beta was initially limited to text messaging and was also available to some AT&T and Verizon customers. The service has since expanded to support limited data access through selected apps, including WhatsApp, Google Maps, AccuWeather, and AllTrails. It is designed to provide a connection in areas where normal cell towers are unavailable, rather than replace a conventional mobile network. However, if SpaceX actually has a plan to serve nationwide, it needs to do more than just satellite networks and actually support on-ground operations. It can also partner up with existing carriers and become a mobile virtual network operator (MVNO). With that said, SpaceX has already spent heavily to support its mobile ambitions. Just last year, the company agreed to acquire wireless spectrum licences from EchoStar in deals worth a combined $19.6 billion. EchoStar's spectrum includes AWS-4, H-Block, and AWS-3 frequencies that could be used for both satellite and terrestrial communications. According to a SpaceX securities filing, the Federal Communications Commission approved the transaction in May 2026, although it is not expected to close until late 2027. There's no official statement by SpaceX for now. Pricing, availability, and other details remain unknown. Source: Financial Times
  • Recent Achievements

    • Week One Done
      xvvxcvv earned a badge
      Week One Done
    • One Month Later
      xvvxcvv earned a badge
      One Month Later
    • Enthusiast
      Xonos went up a rank
      Enthusiast
    • Conversation Starter
      Admir earned a badge
      Conversation Starter
    • First Post
      The_Focal_Point earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      400
    2. 2
      +Edouard
      170
    3. 3
      PsYcHoKiLLa
      127
    4. 4
      neufuse
      69
    5. 5
      Xenon
      66
  • Tell a friend

    Love Neowin? Tell a friend!