Add source Login
Winston Peters and David Seymour trade blows over Fonterra deal

Winston Peters and David Seymour trade blows over Fonterra deal

By Russell Palmer of RNZ New Zealand First leader Winston Peters says his suggestion Fonterra should face more regulation is not a threat but rather “Parliament’s duty”. ACT’s David Seymour says politicians should leave the decision to those “milking cows”, to which Peters bit back: “We know what one end of the cow looks like”. Peters penned an open letter to farmers on Friday morning, having earlier criticised Fonterra’s proposal to sell retail brands like Mainland and Anchor, and other assets, to French company Lactalis. The letter accused the company’s executives of not being transparent and warned that if the deal progressed “then perhaps we need to revisit the regulatory environment”. Speaking to RNZ, Peters denied that warning was in any way a “threat”. He said his letter was intended to alert farmers “to what’s going on”. “I’m not interfering with the farming community or with Fonterra. I’m saying, ‘You have enjoyed by statute and by Parliament the position of a monopoly privilege and now you’re selling it and claiming it’s all of your own right’. No, it’s not. It’s the right of the New Zealand people,” he said. David Seymour argues commercial decisions should be left to farmers, not politicians. Photo / Mark Mitchell “When you ask for regulatory conditions and privileges and then you sell them off to some other country’s advantage with no permanency in terms of benefit to New Zealand - or, dare I say, their children and their grandchildren’s chance to go farming in this country - then it’s the Parliament’s duty to examine the full import of this deal.” In a written statement to RNZ, Regulations Minister Seymour - who’s also ACT leader and deputy prime minister - said New Zealand was not a socialist country, and commercial decisions “should be for business owners, and political decisions for politicians”. “If anyone wants a say on the Fonterra vote, they should earn the right by getting up at 4am and milking cows for a few decades. If they’re not prepared to do that, they should leave it to the people who are.” That comment did not go down well with Peters: “I milked cows almost two decades, and so did Shane Jones, and so did others of us in my caucus. Fonterra's deal could net over $4.2 billion, with farmers voting on the proposal. Photo / 123RF “We actually know what one end of the cow looks like compared to some who don’t.” The suggestion politicians should stay out of business decisions was “marvellous, until you demand privileges from Parliament to give yourself the chance of having an edge to then turn against the national interest for your own narrow advantage”, Peters said. Fonterra rejected RNZ’s requests for interviews but said it would respond to Peters’ letter with a statement soon. A spokesperson also pointed to Parliament records showing it was the select committees that declined to hear from Fonterra, not the other way around. Peters told RNZ that was not good enough. “With respect, Fonterra could have volunteered, regardless of the committee,” he said. “Just because others in the committee have got a perverted idea what free enterprise and capitalism looks like - against the national interest - there’s no reason for them to repeat a mistake that they made when they did that same thing with the Beingmate investment.” Prime Minister Christopher Luxon’s office told RNZ he had nothing to add to his comments on Monday, in which he said politicians should not be telling farmers what to do. “He’s entitled to a view of what he wants, but I’m just saying to you farmers will make that decision, not Winston Peters or not Chris Luxon. We can have our respective reckons and views, that’s fine, but ultimately it’s a decision for farmers and they’re quite capable of making the decision.” The deal is expected to net Fonterra more than $4.2 billion, and pay out $2 per share to farmers - so a smaller farm of 300 to 400 cows producing 100,000kg of milk solids a year could be exp...

There yesterday, gone today?

There yesterday, gone today?

New Zealand and South Seas International Exhibition, 1925-26 The principal (south) elevation of the New Zealand and South Seas International Exhibition, 1925-26. Panorama from L.S. Fanning, The Pictorial History: The N.Z. and South Seas Exhibition Dunedin, Dunedin, 1926. - Text, photographs and concept by Jonathan Howard

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

Just as Windows 10 has reached its end of life (EOL), issues with Windows 11 abound, the most recent an update that broke localhost for some developers, preventing them from accessing web apps running locally on their machines. The October 2025 cumulative update, (KB5066835), addressed security issues in Windows operating systems (OSes), but also appears to have blocked Windows’ ability to talk within itself. Localhost allows apps and services to communicate internally without using internet or external network access. Developers use the function to develop, test, and debug websites and apps locally on a Windows machine before releasing them to the public. “For anyone doing software development, this is huge,” said David Shipley of Beauceron Security. The problem has been widely reported on Microsoft support forums as well as on other developer sites such as Stack Overflow and Stack Exchange. Microsoft has confirmed the bug ; an updated Windows release health page describes the issue and its suggested mitigations. Impacting the way devs do their work KB5066835 is an October 2025 cumulative update for Windows 11 versions 24H2 and 25H2. It was preceded by a preview update, KB5065789, released on September 29, 2025, both addressing issues including problems with print preview in Chromium-based browsers, command time-outs impacting auditing in PowerShell Remoting and Windows Remote Management (WinRM), and persistent error messages in Windows Hello setup. But developers have reported a few unexpected issues as well, including connection failures and HTTP/2 protocol issues impacting various development tools such as ASP.NET and Visual Studio. Mitigation Some developers have been able to get around these significant glitches by uninstalling the KB5066835 package, rebooting, and then pausing Windows updates so it won’t be automatically reinstalled. Others, however, have reported in online forums that their attempts to uninstall KB5066835 were unsuccessful, and that they had to instead remove the previous KB5065789 September package. If neither of those tactics worked, users suggested opening Windows Features and turning off Hyper-V, IIS, Windows Process Activation Service, and .NET Framework 3.5 and 4.8. Microsoft responded by attributing the issue to a “variety of conditions,” including internet connectivity and the “timing of recent update installation and device restarts,” and says it is possible it may not be observed at all in some environments. Its suggested mitigation is via Known Issue Rollback to remove the offending updates; this will be resolved automatically for home and unmanaged business devices, it said, and can be deployed using a special Group Policy in enterprises. The company also suggested trying the following steps: Open “Windows Update” in the “Windows Settings” app. Click on “Check for updates” and allow any updates to install. Restart the device (even if no updates were installed in the previous step). “We are working on releasing a resolution for this issue in a future Windows update,” Microsoft said. “We will provide an update when more information is available.” Disruption and frustration “This is affecting local development as well as business applications,” one user wrote on a Microsoft-hosted forum . They reported that when the update is removed, “everything works again.” The localhost loopback connection is a “fundamental” element of Windows that developers and enterprises quietly rely on every day, explained Erik Avakian , a technical counselor at Info-Tech Research Group. “Localhost serves as a sort of backbone for how many modern apps are built and tested.” When localhost stops working, entire application development environments can be impacted or “even grind to a halt,” causing internal processes and services to fail and stop communicating, he pointed out. This means developers are unable to test or run web applications locally. This issue is really about “denial of service,” where tools and processes dependent on internal loopback services break, he noted. Developers can’t debug locally, and automated testing processes can fail. At the same time, IT departments are left to troubleshoot, field an influx of service tickets, roll back patches, and look for workarounds. “This bug is definitely disruptive enough to cause delays, lost productivity, and frustration across teams,” said Avakian. “All of those equate to real dollars in user time on task and business process disruption.” Microsoft quality control in doubt: Something so fundamental shouldn’t break From an economic impact point of view, software developers may each have lost a half day to a day or more due to this issue, noted Beauceron’s Shipley. “That adds up quickly,” he said. He even went so far as to say that, depending on the number of developers impacted worldwide, this bug could have as large an impact as the widespread CrowdStrike outage in July 2024 that halted flights and took millions of companies temporarily offline. “If people are rolling back this update, which includes security fixes, for high value targets like developers, this creates a huge risk,” said Shipley. Having developers step back from automatic patching and take the old approach of waiting a few weeks before applying patches is “massively more dangerous” today, given the speed at which AI-enabled vulnerability development now operates (15 minutes or less), he noted. “I’d love to see a post-mortem on how this mess happened and if there’s a role here that bad AI code or testing played in it,” said Shipley. Info-Tech’s Avakian agreed that developers are being forced to pick between two bad options: “staying patched and secure [but unproductive] versus staying functional and productive.” This type of issue underscores the importance of quality control and thorough testing by third-party suppliers and vendors before releasing updates to commercial markets, he said. Not doing so can have significant downstream impacts and “erode trust” in the update process while making teams more cautious about patching. “Localhost is really one of the most basic pieces of the Windows networking stack,” said Avakian. “Something so fundamental shouldn’t fall through the cracks when testing update releases.” He pointed out that the situation is also a great reminder to IT teams to stage updates in test environments first, test various critical business processes throughout the enterprise with each update iteration, and build runbooks with rollback plans and dependencies that map to business processes. “When these disruptions are multiplied across dozens or hundreds of dev machines, it can amount to a high cost in time, delays, and coordination of the IT teams,” said Avakian.

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

Just as Windows 10 has reached its end of life (EOL), issues with Windows 11 abound, the most recent an update that broke localhost for some developers, preventing them from accessing web apps running locally on their machines. The October 2025 cumulative update, (KB5066835), addressed security issues in Windows operating systems (OSes), but also appears to have blocked Windows’ ability to talk within itself. Localhost allows apps and services to communicate internally without using internet or external network access. Developers use the function to develop, test, and debug websites and apps locally on a Windows machine before releasing them to the public. “For anyone doing software development, this is huge,” said David Shipley of Beauceron Security. The problem has been widely reported on Microsoft support forums as well as on other developer sites such as Stack Overflow and Stack Exchange. Microsoft has confirmed the bug ; an updated Windows release health page describes the issue and its suggested mitigations. Impacting the way devs do their work KB5066835 is an October 2025 cumulative update for Windows 11 versions 24H2 and 25H2. It was preceded by a preview update, KB5065789, released on September 29, 2025, both addressing issues including problems with print preview in Chromium-based browsers, command time-outs impacting auditing in PowerShell Remoting and Windows Remote Management (WinRM), and persistent error messages in Windows Hello setup. But developers have reported a few unexpected issues as well, including connection failures and HTTP/2 protocol issues impacting various development tools such as ASP.NET and Visual Studio. Mitigation Some developers have been able to get around these significant glitches by uninstalling the KB5066835 package, rebooting, and then pausing Windows updates so it won’t be automatically reinstalled. Others, however, have reported in online forums that their attempts to uninstall KB5066835 were unsuccessful, and that they had to instead remove the previous KB5065789 September package. If neither of those tactics worked, users suggested opening Windows Features and turning off Hyper-V, IIS, Windows Process Activation Service, and .NET Framework 3.5 and 4.8. Microsoft responded by attributing the issue to a “variety of conditions,” including internet connectivity and the “timing of recent update installation and device restarts,” and says it is possible it may not be observed at all in some environments. Its suggested mitigation is via Known Issue Rollback to remove the offending updates; this will be resolved automatically for home and unmanaged business devices, it said, and can be deployed using a special Group Policy in enterprises. The company also suggested trying the following steps: Open “Windows Update” in the “Windows Settings” app. Click on “Check for updates” and allow any updates to install. Restart the device (even if no updates were installed in the previous step). “We are working on releasing a resolution for this issue in a future Windows update,” Microsoft said. “We will provide an update when more information is available.” Disruption and frustration “This is affecting local development as well as business applications,” one user wrote on a Microsoft-hosted forum . They reported that when the update is removed, “everything works again.” The localhost loopback connection is a “fundamental” element of Windows that developers and enterprises quietly rely on every day, explained Erik Avakian , a technical counselor at Info-Tech Research Group. “Localhost serves as a sort of backbone for how many modern apps are built and tested.” When localhost stops working, entire application development environments can be impacted or “even grind to a halt,” causing internal processes and services to fail and stop communicating, he pointed out. This means developers are unable to test or run web applications locally. This issue is really about “denial of service,” where tools and processes dependent on internal loopback services break, he noted. Developers can’t debug locally, and automated testing processes can fail. At the same time, IT departments are left to troubleshoot, field an influx of service tickets, roll back patches, and look for workarounds. “This bug is definitely disruptive enough to cause delays, lost productivity, and frustration across teams,” said Avakian. “All of those equate to real dollars in user time on task and business process disruption.” Microsoft quality control in doubt: Something so fundamental shouldn’t break From an economic impact point of view, software developers may each have lost a half day to a day or more due to this issue, noted Beauceron’s Shipley. “That adds up quickly,” he said. He even went so far as to say that, depending on the number of developers impacted worldwide, this bug could have as large an impact as the widespread CrowdStrike outage in July 2024 that halted flights and took millions of companies temporarily offline. “If people are rolling back this update, which includes security fixes, for high value targets like developers, this creates a huge risk,” said Shipley. Having developers step back from automatic patching and take the old approach of waiting a few weeks before applying patches is “massively more dangerous” today, given the speed at which AI-enabled vulnerability development now operates (15 minutes or less), he noted. “I’d love to see a post-mortem on how this mess happened and if there’s a role here that bad AI code or testing played in it,” said Shipley. Info-Tech’s Avakian agreed that developers are being forced to pick between two bad options: “staying patched and secure [but unproductive] versus staying functional and productive.” This type of issue underscores the importance of quality control and thorough testing by third-party suppliers and vendors before releasing updates to commercial markets, he said. Not doing so can have significant downstream impacts and “erode trust” in the update process while making teams more cautious about patching. “Localhost is really one of the most basic pieces of the Windows networking stack,” said Avakian. “Something so fundamental shouldn’t fall through the cracks when testing update releases.” He pointed out that the situation is also a great reminder to IT teams to stage updates in test environments first, test various critical business processes throughout the enterprise with each update iteration, and build runbooks with rollback plans and dependencies that map to business processes. “When these disruptions are multiplied across dozens or hundreds of dev machines, it can amount to a high cost in time, delays, and coordination of the IT teams,” said Avakian.

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

Just as Windows 10 has reached its end of life (EOL), issues with Windows 11 abound, the most recent an update that broke localhost for some developers, preventing them from accessing web apps running locally on their machines. The October 2025 cumulative update, (KB5066835), addressed security issues in Windows operating systems (OSes), but also appears to have blocked Windows’ ability to talk within itself. Localhost allows apps and services to communicate internally without using internet or external network access. Developers use the function to develop, test, and debug websites and apps locally on a Windows machine before releasing them to the public. “For anyone doing software development, this is huge,” said David Shipley of Beauceron Security. The problem has been widely reported on Microsoft support forums as well as on other developer sites such as Stack Overflow and Stack Exchange. Microsoft has confirmed the bug ; an updated Windows release health page describes the issue and its suggested mitigations. Impacting the way devs do their work KB5066835 is an October 2025 cumulative update for Windows 11 versions 24H2 and 25H2. It was preceded by a preview update, KB5065789, released on September 29, 2025, both addressing issues including problems with print preview in Chromium-based browsers, command time-outs impacting auditing in PowerShell Remoting and Windows Remote Management (WinRM), and persistent error messages in Windows Hello setup. But developers have reported a few unexpected issues as well, including connection failures and HTTP/2 protocol issues impacting various development tools such as ASP.NET and Visual Studio. Mitigation Some developers have been able to get around these significant glitches by uninstalling the KB5066835 package, rebooting, and then pausing Windows updates so it won’t be automatically reinstalled. Others, however, have reported in online forums that their attempts to uninstall KB5066835 were unsuccessful, and that they had to instead remove the previous KB5065789 September package. If neither of those tactics worked, users suggested opening Windows Features and turning off Hyper-V, IIS, Windows Process Activation Service, and .NET Framework 3.5 and 4.8. Microsoft responded by attributing the issue to a “variety of conditions,” including internet connectivity and the “timing of recent update installation and device restarts,” and says it is possible it may not be observed at all in some environments. Its suggested mitigation is via Known Issue Rollback to remove the offending updates; this will be resolved automatically for home and unmanaged business devices, it said, and can be deployed using a special Group Policy in enterprises. The company also suggested trying the following steps: Open “Windows Update” in the “Windows Settings” app. Click on “Check for updates” and allow any updates to install. Restart the device (even if no updates were installed in the previous step). “We are working on releasing a resolution for this issue in a future Windows update,” Microsoft said. “We will provide an update when more information is available.” Disruption and frustration “This is affecting local development as well as business applications,” one user wrote on a Microsoft-hosted forum . They reported that when the update is removed, “everything works again.” The localhost loopback connection is a “fundamental” element of Windows that developers and enterprises quietly rely on every day, explained Erik Avakian , a technical counselor at Info-Tech Research Group. “Localhost serves as a sort of backbone for how many modern apps are built and tested.” When localhost stops working, entire application development environments can be impacted or “even grind to a halt,” causing internal processes and services to fail and stop communicating, he pointed out. This means developers are unable to test or run web applications locally. This issue is really about “denial of service,” where tools and processes dependent on internal loopback services break, he noted. Developers can’t debug locally, and automated testing processes can fail. At the same time, IT departments are left to troubleshoot, field an influx of service tickets, roll back patches, and look for workarounds. “This bug is definitely disruptive enough to cause delays, lost productivity, and frustration across teams,” said Avakian. “All of those equate to real dollars in user time on task and business process disruption.” Microsoft quality control in doubt: Something so fundamental shouldn’t break From an economic impact point of view, software developers may each have lost a half day to a day or more due to this issue, noted Beauceron’s Shipley. “That adds up quickly,” he said. He even went so far as to say that, depending on the number of developers impacted worldwide, this bug could have as large an impact as the widespread CrowdStrike outage in July 2024 that halted flights and took millions of companies temporarily offline. “If people are rolling back this update, which includes security fixes, for high value targets like developers, this creates a huge risk,” said Shipley. Having developers step back from automatic patching and take the old approach of waiting a few weeks before applying patches is “massively more dangerous” today, given the speed at which AI-enabled vulnerability development now operates (15 minutes or less), he noted. “I’d love to see a post-mortem on how this mess happened and if there’s a role here that bad AI code or testing played in it,” said Shipley. Info-Tech’s Avakian agreed that developers are being forced to pick between two bad options: “staying patched and secure [but unproductive] versus staying functional and productive.” This type of issue underscores the importance of quality control and thorough testing by third-party suppliers and vendors before releasing updates to commercial markets, he said. Not doing so can have significant downstream impacts and “erode trust” in the update process while making teams more cautious about patching. “Localhost is really one of the most basic pieces of the Windows networking stack,” said Avakian. “Something so fundamental shouldn’t fall through the cracks when testing update releases.” He pointed out that the situation is also a great reminder to IT teams to stage updates in test environments first, test various critical business processes throughout the enterprise with each update iteration, and build runbooks with rollback plans and dependencies that map to business processes. “When these disruptions are multiplied across dozens or hundreds of dev machines, it can amount to a high cost in time, delays, and coordination of the IT teams,” said Avakian.

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

A mini-CrowdStrike moment? Windows 11 update cripples dev environments

Just as Windows 10 has reached its end of life (EOL), issues with Windows 11 abound, the most recent an update that broke localhost for some developers, preventing them from accessing web apps running locally on their machines. The October 2025 cumulative update, (KB5066835), addressed security issues in Windows operating systems (OSes), but also appears to have blocked Windows’ ability to talk within itself. Localhost allows apps and services to communicate internally without using internet or external network access. Developers use the function to develop, test, and debug websites and apps locally on a Windows machine before releasing them to the public. “For anyone doing software development, this is huge,” said David Shipley of Beauceron Security. The problem has been widely reported on Microsoft support forums as well as on other developer sites such as Stack Overflow and Stack Exchange. Microsoft has confirmed the bug ; an updated Windows release health page describes the issue and its suggested mitigations. Impacting the way devs do their work KB5066835 is an October 2025 cumulative update for Windows 11 versions 24H2 and 25H2. It was preceded by a preview update, KB5065789, released on September 29, 2025, both addressing issues including problems with print preview in Chromium-based browsers, command time-outs impacting auditing in PowerShell Remoting and Windows Remote Management (WinRM), and persistent error messages in Windows Hello setup. But developers have reported a few unexpected issues as well, including connection failures and HTTP/2 protocol issues impacting various development tools such as ASP.NET and Visual Studio. Mitigation Some developers have been able to get around these significant glitches by uninstalling the KB5066835 package, rebooting, and then pausing Windows updates so it won’t be automatically reinstalled. Others, however, have reported in online forums that their attempts to uninstall KB5066835 were unsuccessful, and that they had to instead remove the previous KB5065789 September package. If neither of those tactics worked, users suggested opening Windows Features and turning off Hyper-V, IIS, Windows Process Activation Service, and .NET Framework 3.5 and 4.8. Microsoft responded by attributing the issue to a “variety of conditions,” including internet connectivity and the “timing of recent update installation and device restarts,” and says it is possible it may not be observed at all in some environments. Its suggested mitigation is via Known Issue Rollback to remove the offending updates; this will be resolved automatically for home and unmanaged business devices, it said, and can be deployed using a special Group Policy in enterprises. The company also suggested trying the following steps: Open “Windows Update” in the “Windows Settings” app. Click on “Check for updates” and allow any updates to install. Restart the device (even if no updates were installed in the previous step). “We are working on releasing a resolution for this issue in a future Windows update,” Microsoft said. “We will provide an update when more information is available.” Disruption and frustration “This is affecting local development as well as business applications,” one user wrote on a Microsoft-hosted forum . They reported that when the update is removed, “everything works again.” The localhost loopback connection is a “fundamental” element of Windows that developers and enterprises quietly rely on every day, explained Erik Avakian , a technical counselor at Info-Tech Research Group. “Localhost serves as a sort of backbone for how many modern apps are built and tested.” When localhost stops working, entire application development environments can be impacted or “even grind to a halt,” causing internal processes and services to fail and stop communicating, he pointed out. This means developers are unable to test or run web applications locally. This issue is really about “denial of service,” where tools and processes dependent on internal loopback services break, he noted. Developers can’t debug locally, and automated testing processes can fail. At the same time, IT departments are left to troubleshoot, field an influx of service tickets, roll back patches, and look for workarounds. “This bug is definitely disruptive enough to cause delays, lost productivity, and frustration across teams,” said Avakian. “All of those equate to real dollars in user time on task and business process disruption.” Microsoft quality control in doubt: Something so fundamental shouldn’t break From an economic impact point of view, software developers may each have lost a half day to a day or more due to this issue, noted Beauceron’s Shipley. “That adds up quickly,” he said. He even went so far as to say that, depending on the number of developers impacted worldwide, this bug could have as large an impact as the widespread CrowdStrike outage in July 2024 that halted flights and took millions of companies temporarily offline. “If people are rolling back this update, which includes security fixes, for high value targets like developers, this creates a huge risk,” said Shipley. Having developers step back from automatic patching and take the old approach of waiting a few weeks before applying patches is “massively more dangerous” today, given the speed at which AI-enabled vulnerability development now operates (15 minutes or less), he noted. “I’d love to see a post-mortem on how this mess happened and if there’s a role here that bad AI code or testing played in it,” said Shipley. Info-Tech’s Avakian agreed that developers are being forced to pick between two bad options: “staying patched and secure [but unproductive] versus staying functional and productive.” This type of issue underscores the importance of quality control and thorough testing by third-party suppliers and vendors before releasing updates to commercial markets, he said. Not doing so can have significant downstream impacts and “erode trust” in the update process while making teams more cautious about patching. “Localhost is really one of the most basic pieces of the Windows networking stack,” said Avakian. “Something so fundamental shouldn’t fall through the cracks when testing update releases.” He pointed out that the situation is also a great reminder to IT teams to stage updates in test environments first, test various critical business processes throughout the enterprise with each update iteration, and build runbooks with rollback plans and dependencies that map to business processes. “When these disruptions are multiplied across dozens or hundreds of dev machines, it can amount to a high cost in time, delays, and coordination of the IT teams,” said Avakian.