Fixed: Proxmox, Edge, FSLogix, Trellix, Outlook, OPNsense

Call: DeployEnterpriseEnd-user appsHomelabfrom 2026-10

Call: Deploy. These broke, got fixed during the October 2026 patch cycle, and weren’t security bugs. If you’re still seeing one of them, you’re behind on the fix, and the fix is below.

Proxmox VE kernel 7.0.14-20: Broadcom and Realtek NICs drop off

What broke: proxmox-kernel 7.0.14-20-pve (and -21) broke networking on two NIC families:
- Broadcom NetXtreme-E (bnxt_en): fatal firmware resets, TX timeouts, DMAR/IOMMU faults, and links that flapped or died within minutes. A Proxmox developer called it “widely reported.”
- Realtek RTL8168h (r8169): a PCIe AER/DPC “UnsupReq” error during PHY init, then no carrier, so vmbr0 stayed down.
Who was hit: PVE 9.2 hosts with BCM57412/57414/57416/57502 or RTL8168h NICs.
How it was fixed: Proxmox picked up the upstream bnxt_en DMA-padding fix (applied Oct 7) in 7.0.14-22, and the Realtek reporter confirmed -22 fixed theirs too. Proxmox pointed later stragglers to -23, which carries the updated patch. Go to 7.0.14-23 or later, then remove the old workarounds: kernel pins to -19, and pcie_aspm=off.

Microsoft Edge 155 won’t launch; Edge 154 loses its default search engine

What broke:
- Edge 155: on some managed Windows profiles, Edge wouldn’t start at all after the Edge management service’s scheduled update-and-restart.
- Edge 154: with Default Search Provider policies set as Recommended, address-bar searches stopped working shortly after launch, and Settings showed “––” as the engine.
- Edge 154: “Microsoft Print to PDF” failed too.
Who was hit: Managed fleets (Intune, Group Policy, the Edge management service).
How it was fixed:
- The search bug was fixed in 155.0.4283.45.
- The print issue was fixed in 154.0.4258.48.
- The launch failure was fixed in 156.0.4314.42 (Oct 22).
Move forward to 156, not back.

What broke: After KB5120998 (August 27) and later updates, multi-session hosts showed a black screen at sign-in, and Explorer crashed.
Who was hit: Windows 11 24H2-26H2 Azure Virtual Desktop and multi-session hosts with FSLogix.
How it was fixed: KB5127648 (Oct 13). Install it, then remove the Known Issue Rollback if you deployed one.

Apps that decode AC-3 audio closed unexpectedly

What broke: After the September 22 preview update (KB5124010), older apps and games that use Windows’ built-in Dolby Digital (AC-3) decoder crashed.
Who was hit: Windows 11 24H2-26H2 with legacy media apps.
How it was fixed: KB5127648 (Oct 13).

Trellix EDR client BSODs on recently updated Windows

What broke: The Trellix EDR client for Windows could blue-screen machines:
- KMODE_EXCEPTION_NOT_HANDLED (0x1E) at service startup on recently updated Windows (SEC-212605)
- 0x133 on NUMA hardware (SEC-213041)
- 0x50 (SEC-214689)
Who was hit: Trellix EDR (on-prem) Windows clients older than 4.2.3.6356.
How it was fixed: EDR client 4.2.3.6356, in Trellix’s October 12 release. Update the agent before or alongside the October Windows update.

Classic Outlook: Copilot buttons missing

What broke: Copilot buttons disappeared from classic Outlook. Microsoft said in June that it had fixed this with a service-side change. Then it came back.
Who was hit: Classic Outlook users with Copilot Chat or Microsoft 365 Copilot.
How it was fixed: Microsoft fixed it again on October 19, this time in the client. If the buttons are still missing, turn on File > Options > Advanced > “Show Apps in Outlook”, or create a new profile.

New Outlook: attachments won’t open after an Edge 156 update

What broke: From Oct 28 (16:24 UTC), the new Outlook for Windows failed to open attachments with an error that the file couldn’t be opened, and the “Open” option then disappeared. Microsoft (incident EX1528992) says an Edge 156 update “unintentionally enabled an unnecessary configuration.” New Outlook runs on Edge’s WebView2 runtime, so the browser update broke the mail client.
Who was hit: New Outlook for Windows users. Classic Outlook wasn’t affected.
How it was fixed: Microsoft deployed a fix overnight Oct 28-29 and told users to restart new Outlook. It closed the incident on Oct 29, giving 12:00 UTC that day as the end of impact. Still stuck? Restart new Outlook. Until it opens attachments again, use Save As and open the saved copy.

OPNsense 26.7.8: VPN and dynamic gateways show offline; CA import asks for a private key

What broke: OPNsense 26.7.8 (Oct 30) is a security release, and you want it. One change in it, “allow a single dynamic interface gateway to work for both IPv4 and IPv6,” broke gateways for some people. The first forum report had VPN gateways that wouldn’t start and showed the wrong address family, IPv6 instead of IPv4. OPNsense’s GitHub issue #11117 was titled “26.7.8: VPN Gateway Monitoring Fails.” Separately, importing a certificate or CA wrongly demanded a private key.
Who was hit: Some 26.7.8 installs with dynamic or VPN gateways, especially gateway groups built on them. Plenty of people with outbound VPNs upgraded cleanly, and an OPNsense developer said it hit “a lot softer than initially anticipated.”
How it was fixed: OPNsense reverted the gateway change in a hotfix, 26.7.8_1 (Oct 31), and 26.7.8_2 (Nov 1) also fixed the certificate/CA import regression. Both keep all of 26.7.8’s security fixes. Update now and you land on 26.7.8_2. If you applied the opnsense-patch revert from the forum thread by hand, the hotfix makes it redundant.
One change that stays: for security reasons, 26.7.8 limits each certificate entry to a single certificate. If you kept a chain or bundle in one entry, check it. That isn’t reverted.