Recommended Posts

Wow, a candidate for a Beta :rolleyes: When are they going to release the candidate to the candidate of the Beta? :laugh:

  • Code Freeze: 11/04
  • Builds Start: 11/04
  • QA: 11/04 - 11/09 (estimate)
    • Smoketests and BFTs using Mozmill: (1 person)
    • Manual smoketests, BFT areas, and Other OS Spot Checks: 11/04-11/09 (3 people)
    • Testday: 11/05 (3 people monitoring)
    • Accessibility: On-going (1 person)
    • Top Sites Functionality and Page Load Testing: Before 11/09 (1 people)
    • Updates checks: Before 11/09 (1 person)
      • Manual spot checks as necessary

Seems like tuesday is the day (in Indian system , it would be called 9/11)

Although i have been using Minefield on my very old Office PC and only Beta 6 on my home PC. Beta 7 makes using Firefox on my Home PC enjoyable again.

For now, the speed difference is no longer substantial between Firefox and Opera / Chrome. Page Rendering and JS are still little slower. But i cant live with that, for all the great extensions and awesome bar.

Hello,

As I just D/L and installed the FF4.0b7 RC1 build, but was curious as I wanted to update my sig @mozillaZine Forums--->it use to be:

Mozilla/5.0 (Windows NT 6.0; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

However now when I go to help--->About

resizedmm.jpg

Uploaded with ImageShack.us

Any ideas where a 'string would be'...? lol

Any ideas where a 'string would be'...? lol

It's stupid that they removed the string from the about box, but you can still see it by typing

about: in the urlbar.

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101106 Firefox/4.0b8pre

It's stupid that they removed the string from the about box, but you can still see it by typing

about: in the urlbar.

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101106 Firefox/4.0b8pre

Thanks crispkreme...:) It was getting me kind of annoyed on this nice Saturday afternoon...lol! I could not find it anywhere...

Note: the build strings in main releases (beta, final) will always show Gecko/20100101 now, to avoid 'fingerprinting'.

You answered my next question...lol

As I was wondering why the Beta 4.0 builds showed Gecko/20100101, with (IIRC) Beta 1, 2, 3, 4, 5, and 6..

Thanks Kirkburn

Note: the build strings in main releases (beta, final) will always show Gecko/20100101 now, to avoid 'fingerprinting'.

People were using it as a version identifier for some strange reason, random sites would break every year since they didn't expect the year increase of nightly builds and such.

By freezing it on a set date, they'll force those people to either update their code, or make it never have an issue again (unless they then remove the fake date which I think is the general plan)

People were using it as a version identifier for some strange reason, random sites would break every year since they didn't expect the year increase of nightly builds and such.

By freezing it on a set date, they'll force those people to either update their code, or make it never have an issue again (unless they then remove the fake date which I think is the general plan)

hmm shouldn't they just do it in one go rather than risking two potential breakages?

Taken from buildnotes page. Here is what is left to be done before beta 7.

Final checks before push

Virus check

Update Bouncer

Push to mirrors

  • Wait for email from driver before continuing

Final verify

Push snippets to beta channel

Remove index.html files

Release

Will Beta 7 be the first one with JaegerMonkey? I've been using the nightlies so I haven't kept track of the milestones that well.

Yup.. if no blockers are found. Beta 7 should be released within the next couple of days. looking forward to beta 7 myself.

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

    • No registered users viewing this page.
  • Posts

    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
    • Thanks for the advice guys, I'll give my current GPU a clean and then run the benchmarks to see how similar it is. Hopefully a bit of a clean-out will help it last a bit longer.
    • Pretty sure those will still be in this game. The series' well-explored psychosis themes will return as well.
    • "performance issues? what performance issues?!"
    • Microsoft making much needed change to Windows 11, 10 Patch Tuesday security updates by Sayan Sen Recently, Microsoft delivered its latest Defender patches for Windows 11 ISOs. These definitions are released from time to time alongside the general security updates available during Patch Tuesday. Speaking of Defender, the company has now announced another important change that affects how security updates are delivered to enterprise devices running Windows. According to a recent announcement, Microsoft Defender for Endpoint's endpoint detection and response (EDR) updates will no longer be bundled with the monthly Windows security updates or Patch Tuesdays. Instead the company is shifting delivery of these updates to Microsoft Update, bringing EDR servicing in line with several other Microsoft Defender components. If you recall, Microsoft last year moved PowerShell updates to Microsoft Update (MU) as well since it provides automatic updates for Microsoft products and services. Thus the move is intended to allow Microsoft to deliver EDR improvements and security enhancements independently of the OS's regular monthly update cycle; this should enable faster deployment of protection updates without requiring organizations to wait for the next Patch release. For those unfamiliar, Microsoft Defender for Endpoint's EDR capabilities are designed to help organizations detect, investigate, and respond to advanced threats across managed devices. Keeping these components updated is critical for maintaining protection against evolving attack techniques. The rollout has already began for Windows 10 devices in late May 2026 (last month) and Microsoft says it will gradually expand support to Windows 11 and the remaining supported Windows versions over the coming months. The company expects deployment across Windows 10 and Windows 11 to be completed by fall 2026 or around Q3 of this year. Once the transition is complete, EDR updates will be delivered through Microsoft Update using KB5005292, provided the required prerequisite updates have already been installed. Microsoft is also introducing a new Defender Update Service as part of the change. Following installation of the first update, devices will automatically create a new directory located at %ProgramData%\Microsoft\Microsoft Defender\Defender Update. Microsoft notes that restarts may occasionally be necessary in case of "rare" failure scenarios. For most organizations, the tech giant says no action will be required as long as Microsoft Update is already permitted within their update management strategy. Admins who rely on manually deployed update packages, however, will need to adjust their processes to ensure the new Defender update package is included. Microsoft also recommends reviewing internal documentation and notifying helpdesk and security operations teams about the updated delivery mechanism to avoid confusion during the transition. As a prerequisite, the tech giant notes that systems must be running Sense version 10.8798.25857.1000 or later and have one of the following Windows updates (or later) installed: Win11 24H2 KB5062660 (2025-07 Cumulative Update Preview) Win11 23H2 KB5062663 (2025-07 Cumulative Update Preview) Win11 22H2 KB5062663 (2025-07 Cumulative Update Preview) Win10 22H2 KB5062649 (2025-07 Cumulative Update Preview) Win10 1809 KB5063877 (2025-08 Cumulative Update) Server 2019 KB5063877 (2025-08 Cumulative Update) Server 2022 KB5063880 (2025-08 Cumulative Update) Server 2025 KB5063878 (2025-08 Cumulative Update) As always, organizations should verify that their update policies align with the new servicing approach before the broader rollout reaches all supported Windows platforms later this year. In case of major problems, the EDR update can be rolled back to the inbox version stored in %ProgramFiles%\\Windows Defender Advanced Threat Protection (ATP) using: MpCmdRun.exe -RevertMde -Product Edr -ToVersion Inbox For those who have access to the Microsoft 365 Admin Center portal, you can view the message here under ID MC1381119.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      248
    3. 3
      Steven P.
      73
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!