Recommended Posts

I do not think Build 10036 can be the next build released to Insiders based on what Gabe Aul has said and the and the timeline of the builds created.

 

Below are my notes and analysis as to why I think Build 10039 is probably the next PC build Insiders will get, assuming that Microsoft doesn't find another blocking bug.  I am assuming that the builds information on BuildFeet.net, specifically https://buildfeed.net/lab/fbl_impressive/, is accurate.

 

10.0.10036.0.fbl_impressive.150306-2322 (Build mentioned on Monday, March 9th, Blogging
                                                          Windows blog post as being tested and again being
                                                          referred to by Gabe in his 03/10/2015 11:06 pm
                                                          EDT Twitter post.)

 

On Monday, March 9th, Gabe posted the article on Blogging Windows  where he said "Today is 3/9 and we

  • Like 3

Why spend that much time/research/effort into something that ultimately won't matter. When the new build is released, probably this coming week, you and I will both know the build number but I would have put in 0 amount of time trying to figure it out but you would have wasted a bunch of time for what?

Why spend that much time/research/effort into something that ultimately won't matter. When the new build is released, probably this coming week, you and I will both know the build number but I would have put in 0 amount of time trying to figure it out but you would have wasted a bunch of time for what?

I swear this is a religion for some people.

"When will the holy Gabe unleash his newest blessings upon us?"

 

Except everyone gets all mad and entitled when the holy Gabe doesn't release in a timely fashion.

Why spend that much time/research/effort into something that ultimately won't matter. When the new build is released, probably this coming week, you and I will both know the build number but I would have put in 0 amount of time trying to figure it out but you would have wasted a bunch of time for what?

 

I don't see what's the problem in him using his time on a passion of his, in this case Windows alphas/betas. :)

 

And I did read his entire post, I like Windows beta's and read everything associated with them, nothing wrong with that :)

I swear this is a religion for some people.

"When will the holy Gabe unleash his newest blessings upon us?"

 

Except everyone gets all mad and entitled when the holy Gabe doesn't release in a timely fashion.

 

I'd just like a build without a crappy UI for both the desktop and mobile scenarios. Gabe Aul is just the beta coordinator. He doesn't control what gets released as far as I know.

I'd just like a build without a crappy UI for both the desktop and mobile scenarios. Gabe Aul is just the beta coordinator. He doesn't control what gets released as far as I know.

 

I think he does have the control or say. He was even quoted as saying he'd try to release a new build had the Seahawks won the Superbowl. But being a "beta coordinator" means in my eyes, he has more control or say then that.

 

No, Eric please don't think I'm not bashing on you. I just see things differently is all ;)

I think he does have the control or say. He was even quoted as saying he'd try to release a new build had the Seahawks won the Superbowl. But being a "beta coordinator" means in my eyes, he has more control or say then that.

 

No, Eric please don't think I'm not bashing on you. I just see things differently is all ;)

The seahawks was regarding windows 10 phone beta and releasing a week early than plan.

Build 10041 has been released!

Last Thursday, Gabe said the following...

 

At 1:29 pm EDT on March 12th, Gabe said "We have a good build candidate with some new features I think you'll like. Running through our internal rings now." (see https://twitter.com/...072479338196992)

 

At 1:32 pm EDT on March 12th, Gabe said "I don't want to share the blocking bug info because it will just turn into a debate, but we decided to fix-forward in new build." (see https://twitter.com/...073219427332097)

 

Based on those statements, I thought they had to be targeting Build 10039.  After all, it was created the day before on Wednesday evening and Build 10040 from Thursday night had not been created yet, nor Build 10041, which was created Friday night.

BUT, when no new fbl_impressive builds were created in the labs on Monday or yesterday, I was wondering if they might end up releasing Build 10040 or 10041.  That is exactly what they did.  At least we are getting the newest fbl_impressive build that we know of!

 

Go get your bits!  :)

  • Like 1

Why spend that much time/research/effort into something that ultimately won't matter. When the new build is released, probably this coming week, you and I will both know the build number but I would have put in 0 amount of time trying to figure it out but you would have wasted a bunch of time for what?

i was thinking the same thing. it's just a build of an operating system!

 

anyway, it was 10041 so the original guess was wrong anyway.

This topic is now closed to further replies.
  • 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!