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

    • A coalition of publishers sued OpenAI and Microsoft over scraping content without consent by Hamid Ganji Image via Depositphotos.com AI companies often rely on readily available internet content to train their chatbots and provide users with instant answers. This method of AI training is fast and relatively inexpensive, but using a website’s content without permission or compensation is not something publishers like to see, and this is exactly why Microsoft and OpenAI are now being sued. As reported by Bloomberg, a group of publishers that collectively own nearly 400 newspapers has filed a lawsuit against OpenAI and Microsoft. The coalition argues that the two companies scraped their content to build AI chatbots like ChatGPT and Copilot without paying any compensation. The complaint, filed in the U.S. District Court for the Southern District of New York, argues that while AI products have generated billions of dollars in market value using publishers’ work, none of that value has been shared with the publishers. The plaintiffs are seeking statutory damages and injunctive relief for alleged copyright infringement and violations of the Digital Millennium Copyright Act. “Defendants systematically and secretly crawled the Publishers’ websites—including content behind paywalls and other access restrictions—and copied the Publishers’ articles, stories, and other original works onto their own servers without authorization,” the complaint states. The publishers also described the AI boom as a “death knell for local journalism” if AI companies that scrape content for free are not held accountable. Former New Jersey Attorney General Matthew Platkin and his law firm, Platkin LLP, are representing the publishers. “Our models empower innovation, are trained on publicly available data, and are grounded in fair use,” OpenAI spokesperson Drew Pusateri told Bloomberg. This is not the first lawsuit involving the unauthorized use of publishers’ content by AI firms, but it is one of the largest coalitions ever formed against the free use of content by AI chatbots. In 2024, OpenAI and Microsoft also faced a similar lawsuit from eight newspapers that claimed AI products were benefiting from their content without permission.
    • Rufus alternative Ventoy now supports Windows 11's mandatory update, fixes major boot bug by Sayan Sen While Microsoft has its own official Media Creation Tool used for making bootable USB media, there are some popular third-party utilities as well which offer additional options like bypassing system requirements, Microsoft Account creation, and more. One of these is Ventoy, and the software has received its latest update today. In fact, the app actually got a slew of updates over the last couple of days, three version releases in total, to be specific. The first release, version 1.1.13, was pulled as there was some unspecified error in the update, and as such, the corrected version 1.1.14 was pushed out. Following that on very short notice, 1.1.15 was published as well. For those unfamiliar, Ventoy is an open-source utility that lets users create a bootable USB drive once and then simply copy ISO, WIM, IMG, VHD, or EFI files onto it without repeatedly formatting the drive. It supports both legacy BIOS and UEFI boot modes, Secure Boot, and a wide range of operating systems, making it one of the most versatile tools in the category. The biggest change in version 1.1.14 is an updated Secure Boot shim file aimed at resolving the UEFI CA 2023 issue, which is basically a compatibility problem that has affected Secure Boot environments on some systems. If you recall, we reported about severe boot issues on HP devices following the release of updated Secure Boot 2023 keys. For anyone who may not be aware, back in early 2024, Microsoft announced that it was updating Secure Boot keys as they were going to become 15 years old in 2026, which is also when they are set to expire. As such, the new 2023 certificates have been rolling out with the newest Windows 11 updates. Updated boot manager and Secure Boot certificates are crucial for protection against malware like bootkits. These are mandatory updates. Alongside that, the VentoyPlugson graphical plugin configurator was updated in sync with the release. The update also introduces a new VTOY_SECURE_BOOT_POLICY option within the Global Control plugin, giving users more flexibility in managing Secure Boot behavior. Ventoy has also received a fix for a startup issue when Secure Boot was disabled. Microsoft does officially allow users to boot systems without Secure Boot as long as the PC is Secure Boot capable. The full changelog is given below: Update secure boot shim file to solve the UEFI CA 2023 issue. The new release use a new CA, so you need to enroll the new key for the first boot time. VentoyPlugson update synchronously. Global control plugin add a VTOY_SECURE_BOOT_POLICY option. Fix the boot issue when Secure Boot is disabled in the UEFI firmware. You can download the latest version of the app here on Ventoy's official GitHub repo or from Neowin software stories.
    • Windows 11 is fine, no issues on any of the machines I've run it on since release. The stricter security requirements are a good thing, sometimes the baseline needs to change and people will winge, but it is what it is. Happened with the move from 9x to NT - broke compatability Happened with XP SP2 when security started to become a serious consideration Certainly happend with Vista that brought in UAC, the concept of not running as admin (something that has been the norm in Linux/Unix from pretty much the start) and a completely new driver stack. Windows 11 will probably get looked back at as the point where even consumer and SMB IT was dragged kicking and screaming into a somewhat secure by default configuration.
  • Recent Achievements

    • Rookie
      krychek57 went up a rank
      Rookie
    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      441
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      134
    4. 4
      Michael Scrip
      78
    5. 5
      Xenon
      77
  • Tell a friend

    Love Neowin? Tell a friend!