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

    • Payday TWO!! Is 13 years old man I feel old - I remember trying it out and if I did not know I would say 5-6 years ago or something
    • Payday 2 engine upgrade adds 64-bit and DX11 support, drastically shrinks install size by Pulasthi Ariyasinghe Payday 2, the most popular entry in the heisting game franchise, is getting a surprising update after all these years. This is slated to be a complete engine upgrade that will enhance almost every aspect of the 13-year-old title, targeting performance, loading times, file size, rendering backend, and more. Developer Sidetrack Games is planning a beta to test out the new version ahead of the full public launch. The development team today revealed that the long-awaited upgrade to the 64-bit architecture is happening with this Diesel 3.0 engine update. By letting the game use more ram than 4GB, it is said to improve stability and compatibility on most hardware. It should also help modders in the long term with implementing larger changes too. "While many of the changes are made on the backend and not everything will be visible to you guys because it is a massive rewrite of the entire codebase, there will be a lot of things that you can look forward to," Sidetrack explained. Payday 2 will also hop over from DirectX 9 to 11. Instead of visual improvements, this is slated to reduce the amount of VRAM used by the title, letting more lower-end hardware access the title and run it better. Since these changes would require a complete redownload of the game anyway, Sidetrack says it has revamped "the game's packaging and bundling system." This should reduce the installation size from 86GB to 32GB. "So, now it's time to finally move the game to your SSDs," added the studio. The Payday 2 Diesel Engine 3.0 update is entering open beta on June 30 for Steam users. No console release plans were announced today. Sidetrack Games says it has been working on this complete rewrite of the codebase for the last nine months. While these changes should break most mods, the studio encouraged modders to use the beta period to repair their creations with support from the development team.
  • Recent Achievements

    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      440
    2. 2
      +Edouard
      195
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      68
  • Tell a friend

    Love Neowin? Tell a friend!