Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

WOW lol

has anyone tryed that yet, just installed the service pack 1 via WU, no timebombs in winver

but is it me or is there a huge bug.

someone print screen there desktop and try pasteing it into paint, i get garbled graphics lol

I have done it already but no "garbled graphics" for me.

It's just crazy to think all that... just relax yourself and wait a few more... you'll get what you seek soon.

I hate Vista, I can wait, no rush for me to put it on, but would like to know if SP1 final makes Vista work in the cases I use it.

If you want me to relax, send me on vacation :D

the fact that you can't get the RTM is irrelevant. you'd still have to uninstall the RC first. as for what happens if you don't? sorry i don't know. :p

i'm pretty sure "winver" will tell you the expiry date. just uninstall it before then. :)

I can't uninstall it as I'm using it now, but I won't have access to the PC for a year after Saturday.

BTW, build 18000 aka SP1 RTM doesn't expire

I don't have the RTM, and I'm not getting some spurious version.

hmmm.. crosses fingers that I don't end up with an egged PC.

I can't uninstall it as I'm using it now, but I won't have access to the PC for a year after Saturday.

well put the clock forward a year right now and reboot. you'll have your answer then. :p

on a more serious note, just make sure you backup any important files before saturday. then whatever happens really won't be of much consequence. :)

Well I did that registry tweak back on page 16 and now it's offering me RC1 one, and it links to the old SP1 page and doesn't note the KB number. Is this correct?

That's totally correct. The final RTM build has NOT been made available, hence all you will get is the last refresh build.

That's totally correct. The final RTM build has NOT been made available, hence all you will get is the last refresh build.

And you haven't considered that maybe the latest refresh build is what they used for RTM?

I'll just quote myself in here:

The 6001.18000.080118-1840-build is the RC1 Refresh 2 (a.k.a RC3) at least. But I somehow have a gut-feeling that's the build they sent to RTM. Wild speculations I know, but is plausible.

No one will ever know 100% before MS releases it on connect (if they do that), or comes with a statement. Afaik there is no confirmation from MS that the 080118-1840-build had a huge bug either.

I'm using a slipstreamed vlited 64-bit version of this, and haven't noticed any problems with it (Didn't have any problems with the first RC either though).

And you haven't considered that maybe the latest refresh build is what they used for RTM?

Yes, its possible.

But until the final comes out from an OFFICIAL source, it's only that. Speculation.

If it's the same build - why not release it now on MSDN/Connect? Advanced users and OEMs should be able to get working now with it.

Sorry, still not buying it. For now, the SP1 final build is not confirmed.

If it's the same build - why not release it now on MSDN/Connect? Advanced users and OEMs should be able to get working now with it.

Isn't RC Refresh 2 (aka a possible RTM with my loose logic) released on MSDN/Connect? Microsoft works in mysterious ways, so there's no telling. Everybody assumed the desember leak of Vista was bogus, then it turned out it was the same thing available in stores in february.

That's totally correct. The final RTM build has NOT been made available, hence all you will get is the last refresh build.

As I understand it they are most likely one and the same, except that Microsoft hasn't officially released it with the label "RTM" yet. We'll only know for sure once they release RTM and/or make an announcement. But it appears we may have to wait till mid-March for that.

Isn't RC Refresh 2 (aka a possible RTM with my loose logic) released on MSDN/Connect? Microsoft works in mysterious ways, so there's no telling. Everybody assumed the desember leak of Vista was bogus, then it turned out it was the same thing available in stores in february.

Yes, RC R2 is on MSDN/Connect. (The POSSIBLE rtm build, but not confirmed)

The December leak of Vista was the same as the retail because Vista came out in November for OEMs & Businesses. :|

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

    • No registered users viewing this page.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • 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
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      213
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!