Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

When will people learn, DON'T DOWNLOAD LEADKED FILES I would not have installed it to be honest but people will jump into the fire and get burned.

Oh it's funny how misinformed you are...

Yeah. As much as I'd like to use the leaked slipstream'd ISO, I'm a bit wary without seeing official MD5 sums from MS proving its not been tampered with in anyway. Call me paranoid but its not something I'd feel safe putting my legal product key in.

As I mentioned in the other thread:

Actually, if you extract the files inside the exe using for example, Windows6.0-KB936330-X86.exe /x , then you'll see the inside files are exactly identical to the 18000 ones that are floating around so the *only* difference is the packing exe that MS used. Also worth pointing out is the 18000 ones that are floating around have the exact same MD5 that reviewers got so they're legit too, only difference being MS just used a different packing exe for the bits on the OEM site and on Connect apparently.

After Install SP1 my laptop won't wake up from sleep

funny, you should be a beta tester.....lol. SP1 is running good for me. I've not had a problem at all. I wasn't having problems prior to RTM version either so...It really has taught me that updating your hardware goes well with Vista working well for you.

So there are a couple of SP1 installers build on 19 and 31 of Jan. Both 18000 builds final (time 1840 and 2040 the latest one).

But it is said (at least for the 1st installer) that your machine can get gaught in a reboot loop (when SP1 is updating drivers?) and

also there are some problems when installed on the Media Center.

What about the DVD images of Vista that have integrated the SP1:

6001.18000.080118-1840_x86fre_Client_en-us-FRMCFRE_EN_DVD.iso (for example) are these also affected too?

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
      455
    2. 2
      +Edouard
      206
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      68
  • Tell a friend

    Love Neowin? Tell a friend!