Windows Vista Service Pack 1 RTM x86 leaked


Recommended Posts

its in the Wild

Microsoft Windows Vista SP1 Update 32Bit RTM Build 6001 18000 Read NFO - nDn

come on MS release it NOW!!!!!

yup just seen that myself on loggie.com lol so is 18000 the confirmed RTM build, then, but does this build have the driver problem?

it's ready as is. it contains the pre-requisite updates within the file. :)

Thanks.

"and so, the non believers were cast into the pit of doom and forced they were to play forever more, unsold copies of Daikatana!!"

Daikatana? Seriously? Barbie's Farm, ok, but Daikatana? Sheesh...

Having read though virtually this entire thread, I still can't be sure which of these builds is RTM:

6001.18000.080118-1840

6001.18000.080126-2040

The RTM build has gone out to reviewers, and as Smitty pointed out on the neowin comments, Paul Thurrott's screenshots of the final RTM include a shot of the registry holding the build numbers.

http://www.winsupersite.com/showcase/winvi...sp1_screens.asp

bottom right picture shows :

BuildLab : 6001.longhorn_rtm.080118-1840

BuildLabEx : 6001.18000.x86fre.longhorn_rtm.080118-1840

The RTM build has gone out to reviewers, and as Smitty pointed out on the neowin comments, Paul Thurrott's screenshots of the final RTM include a shot of the registry holding the build numbers.

http://www.winsupersite.com/showcase/winvi...sp1_screens.asp

bottom right picture shows :

BuildLab : 6001.longhorn_rtm.080118-1840

BuildLabEx : 6001.18000.x86fre.longhorn_rtm.080118-1840

That matches my registry perfectly and i've done the hack to dl it from windows update.

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

    • No registered users viewing this page.
  • Posts

    • finally [Taskbar] Taskbar customization just got easier. As we continue to make improvements to the Taskbar experience mentioned last month, we've introduced a dedicated Taskbar Size setting, making it simpler to find, understand, and personalize your ideal taskbar experience.
    • Let me get this straight... It was a web interface for Gmail, so if privacy at Google wasn't concerning enough you'd be going through two companies. And their big feature was the very thing that would make people consider dumping Gmail.
    • 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
  • 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!