7232.0.amd64fre.winmain.090610-1900.client_en-us.ultimate.vhd


Recommended Posts

The claim is obviously bull****, Microsoft has never shown any interest in doing anything like that before, and just don't care.

If they wanted to though, sure, they could easily put "tracking software" in it. They just have to build the final version with a different setting, no problem at all. That these builds have any chance of being the exact binaries that end up on the final media has a probability of about 0.

It is true that the Win7 builds include the possibility for tracking, and some traffic indicate that data is being sent to ms, but I doubt the claim that this date is being used for other that improving the products by gathering usage statistics.

:)...

Thanks for posting that wallpaper!

At first it looks tacky... but really it's not bad for the default wallpaper. Clearly they're serious about pushing the Windows brand, and from a distance the Windows logo placed on a gradient background resembles that of their TV ads, although with different colours of the Windows logo colour spectrum. And from a closeup perspective, there's some interesting bits in the logo: a tree, a butterfly, grass, and a dot matrix.

My only complaint would be how the logo doesn't have a border, light flare, or shadow behind it. Maybe I'm wrong in that it looks better without anything behind it.

The fish was nice while it lasted... and it was still a clever joke. ;)

It's just one of many wallpapers, so no biggy really. Besides everyone here changes it anyways. I have a growing wallpaper folder which I'm going to have win7 change automatically per-day. Though it would've been nice if there was a "change at startup" option. But that's not a big problem really.

It is true that the Win7 builds include the possibility for tracking, and some traffic indicate that data is being sent to ms, but I doubt the claim that this date is being used for other that improving the products by gathering usage statistics.

Well, there's CEIP and error reporting. Both are opt-in in the RC, but I dunno about the pirated builds.

Oh yeah! Another build! And 1 more build above 7231 too! Gosh, this is just fantastic!

[/sarcasm]

7231 is x86 only, and 7232 atm is x64, x86 unlikely to leak as these are all internals. Keep the sarcasm yourself lol.

Seems no more leaks until next week, maybe the RTM final by then.

Does VHD stand for Valvular Heart Disease or virtual hard drive.. uh... er... what?

So if its a virtual hard drive, does it mean that this is just a bunch of random files from a hard drive from the developers at MS? im lost and confused, ha. new to the entire "VHD" thing :p

http://en.wikipedia.org/wiki/VHD_(file_format)

:)

Does VHD stand for Valvular Heart Disease or virtual hard drive.. uh... er... what?

So if its a virtual hard drive, does it mean that this is just a bunch of random files from a hard drive from the developers at MS? im lost and confused, ha. new to the entire "VHD" thing :p

http://en.wikipedia.org/wiki/Valvular_heart_disease

:D

You can create VHD files which are used by Virtual PC in disk management a new feature of Windows 7 or you can image a VHD direct to a empty harddisk, It's an image so your OS is already installed and setup, base OS anyway. So you can be up and running with a VHD within a few minutes.

Then all you have to do is install drivers, software etc.

Difference in security between a ISO and a VHD is that VHD's, people can deploy files within the image, spyware, viruses, depends what group releases this image.

ISO, well it's upto you to find an untouched one or a modified one, depends on what risks you would like to take, but untouched is the way to go.

VHD's are great for getting up and running really fast, as long as the image is safe.

To do a small summing up here:

Seems leakers now on leaking internals, they have to first install it to remove the tracing elements in the install log so they won't be caught, and then sort of compile it to a VHD. It's because win7's disk manager can mount a VHD, so people could actually run the OS by fixing the BCD entries, else they can also image the VHD and restore it to drive C, and run the OS like it's installed normally on drive C. These operations wouldn't be possible on ISO's.

SoLoR had posted on how to convert the VHD to a installing ISO on the previous page, but you had to know how to handle WAIK and ImageX.

He also uploaded the ISO for BT, vasill in tor_ru had uploaded his make, both are people of credit, just make sure you match the MD5's..... and enjoy. :D

To do a small summing up here:

Seems leakers now on leaking internals, they have to first install it to remove the tracing elements in the install log so they won't be caught, and then sort of compile it to a VHD. It's because win7's disk manager can mount a VHD, so people could actually run the OS by fixing the BCD entries, else they can also image the VHD and restore it to drive C, and run the OS like it's installed normally on drive C. These operations wouldn't be possible on ISO's.

SoLoR had posted on how to convert the VHD to a installing ISO on the previous page, but you had to know how to handle WAIK and ImageX.

He also uploaded the ISO for BT, vasill in tor_ru had uploaded his make, both are people of credit, just make sure you match the MD5's..... and enjoy. :D

No, these builds simply originated as vhd from microsoft.

P.S. One of the posters (a reliable source) from torrents.ru has informed of a new compile added to the win7_rtm branch: 7260.0.090612-21xx

No, these builds simply originated as vhd from microsoft.

That would explain why we're only seeing .vhd files after 7229.

P.S. One of the posters (a reliable source) from torrents.ru has informed of a new compile added to the win7_rtm branch: 7260.0.090612-21xx

Interesting... is that one an installable .iso or also just a .vhd?

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

    • No registered users viewing this page.
  • Posts

    • 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.
    • 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 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.
    • 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
  • Tell a friend

    Love Neowin? Tell a friend!