windows 7 build 7061 out int the wild ?

By Mark-b
in The Fast Ring (Insider Previews)

 Share

Recommended Posts

Rookie

Mark-b

Posted
Posted

Good evening!

there are many sources saying that build 7061 of windows 7 is now released and out "in the wild" but no one has tested it yet. Is it true ? this build is an RC- Escrow of the OS. WTH is an RC-Escrow ? :o

sources :http://news.softpedia.com/news/Windows-7-B...09-106822.shtml

Collaborator

ShawnB

Posted
Posted
WTH is an RC-Escrow ? :o

"An escrow build, according to Microsoft sources, means code development is ceased as developers and beta testers hunt for recall class bugs. The escrow code is considered the release to manufacturing code."

-- Taken from here: Article about Windows 2000 RC :)

I'm not saying that 7061 is an escrow build or the RC, just answering your question.

Mentor

gate1975mlm

Posted
Posted
Bad?

Something must be wrong with your system..., the OS appears to be very stable and complete, except for some minor issues that are still being worked out.

I agree with you Build 7057 is by far the best build of Windows 7 I have used so far!!! :)

Build 7057 fixes almost all the bugs I have found in early builds!

Veteran

REM2000

Posted
Posted
I agree with you Build 7057 is by far the best build of Windows 7 I have used so far!!! :)

Build 7057 fixes almost all the bugs I have found in early builds!

Judging from the comments in the forums, it seem that more people have had problems with 57 than the earlier builds.

Enthusiast

wiggly1uk2000

Posted
Posted
Judging from the comments in the forums, it seem that more people have had problems with 57 than the earlier builds.

Putting opinion and hyperbole aside you've hit the nail squarely on the head. The evidence in the forum speaks for itself.

For everyone else the fact is that whether or not you've encountered issues with 7057 they exist in abundance. For those that find 7057 to be wonderful or the best build so far it simply means you haven't encountered the bugs yet or use your PC in ways that are less likely to reveal them.

Sorry, but I get annoyed when people (like xendrome) suggest that those encountering issues must have some problem with their installations. If a number of people are reporting the same bugs (as they are with this build) then the evidence would suggest otherwise.

7057 shows the general direction MS are taking and I think it's a good one but they still have to squash some serious bugs and not get carried away with trimming the cake before it's fully baked.

Veteran

HistoricalNeowin

Posted
Posted
Sorry, but I get annoyed when people (like xendrome) suggest that those encountering issues must have some problem with their installations. If a number of people are reporting the same bugs (as they are with this build) then the evidence would suggest otherwise.

Sorry, but I get annoyed when people (like wiggly1uk2000) use branch builds then wonder whey they're buggy. It's not a release build, that's what happens!

Enthusiast

wiggly1uk2000

Posted
Posted
Sorry, but I get annoyed when people (like wiggly1uk2000) use branch builds then wonder whey they're buggy. It's not a release build, that's what happens!

Actually I accept the bugs with good grace (and I would even for an official public build), report them here for the benefit of others and then move on. Are we just supposed to say every build is wonderful when it's not? If there's a bug why on earth would anybody NOT mention it here in the Windows 7 beta forum??? :blink:

Personally I've no complaints about 7057 and I think the general direction of Windows 7 is very positive but I reserve the right to post about any bugs I find regardless of whether or not it's an official public build. Neowin have not as far as I know limited the Windows 7 forum to build 7000. Even people close to MS have posted here regarding other builds.

Experienced

Rickkins

Posted
Posted
I'm not so excited considering how bad 7057 was.

Concur....7057 was faster, but seems to freeze alot.

I did a deep/full format first. And, my system is reasonably current; phenom II x4- 810, with 4 gigs of ram.

Plus, 7048 ran like a dream....zero issues that weren't merely me being unable to figure something out. Zero freezes...

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors

      By Co-ords · Posted

      That made me laugh! Thank you
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors

      By Karthik Mudaliar · Posted

      Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • OpenAI and Broadcom unveil Jalapeño, a new AI chip built for LLM inference

      By margrave · Posted

      Because of what they have done to VMware I will never buy anything Broadcom again.
    • AMD releases hotfix for driver install issues on Windows 10 PCs

      By TarasBuria · Posted

      AMD releases hotfix for driver install issues on Windows 10 PCs by Taras Buria Earlier this week, AMD released an important graphics driver update. Version 26.6.2 brought AMD FSR 4.1 support to the previous-gen Radeon lineup, the RX 7000 series, giving users better upscaling tech that was previously locked to the newest GPUs. However, the driver turned out to be a little buggy, with users reporting installation issues on systems still running Windows 10. AMD quickly acknowledged the bug and today released a hotfix to resolve the problem. The AMD 26.6.3 Hotfix update is now available for download from the official website. Given that it is a hotfix release, it has only one change in its release notes: AMD announced the update on its official X account and added that a WHQL driver update with the necessary fixes would be released next week. Meanwhile, users can apply the hotfix or roll back to the previous driver using the official AMD Cleanup Utility. You can download AMD Software: Adrenalin Edition 26.6.3 Hotfix Preview Driver from the official website here. It is compatible with all currently supported graphics cards and 64-bit Windows 10 and 11. Full release notes are available on the same page.
    • Windows 11 is now five years old

      By Nick H. · Posted

      With Microsoft now listening to its core audience and acting upon received feedback, fans can finally expect a much better version of Windows 11 than what was available five years ago. Here is to five more years, Windows 11! I guess we all need a good laugh now and again...

  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In

  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!