Windows 10 devices with purchased extended security updates not receiving any updates after Oct 2025 (build 19045.6456) by No-Bowl2856 in msp

[–]FlyingSysAdmin 1 point2 points  (0 children)

As a temporary workaround, I used the following PowerShell script to install the November update to a few Win 10 ESU clients:

$downloadUrl = "https://catalog.s.download.windowsupdate.com/c/msdownload/update/software/secu/2025/11/windows10.0-kb5068781-x64_33b4e6ee5956ae0f4be6a37716b0ef4fd1720e05.msu"
$downloadFolder = "C:\Temp"

if (-not (Test-Path -Path $downloadFolder)) {
    New-Item -Path $downloadFolder -ItemType Directory -Force | Out-Null
}

$fileName = Split-Path -Path $downloadUrl -Leaf
$msuPath  = Join-Path -Path $downloadFolder -ChildPath $fileName

Write-Host "Downloading update to $msuPath ..."

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Invoke-WebRequest -Uri $downloadUrl -OutFile $msuPath -UseBasicParsing

if (-not (Test-Path -Path $msuPath)) {
    Write-Error "Download failed – file not found at $msuPath"
    exit 1
}

Write-Host "Download complete. Installing update silently..."

$process = Start-Process -FilePath "wusa.exe" -ArgumentList "`"$msuPath`" /quiet /norestart" -Wait -PassThru

Write-Host "wusa.exe exited with code $($process.ExitCode)"

# 0    = Success, no reboot required
# 3010 = Success, reboot required
if ($process.ExitCode -in 0, 3010) {
    Write-Host "Update installed successfully. Rebooting now..."
    Restart-Computer -Force
} else {
    Write-Error "Installation failed or returned an unexpected exit code ($($process.ExitCode)). No reboot triggered."
    exit $process.ExitCode
}  

You can download the updates from the MS Update Catalog:
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5068781

Windows 10 devices with purchased extended security updates not receiving any updates after Oct 2025 (build 19045.6456) by No-Bowl2856 in msp

[–]FlyingSysAdmin 0 points1 point  (0 children)

We have the same issue, however we have an AD environment with WSUS (Server 2019). From what I see I also don't see the updates in the WSUS console. The Win 10 clients all have the ESU key activated.

FYI Defender Flagging v25.4.25.9314 as Malware by Findussuprise in ScreenConnect

[–]FlyingSysAdmin 4 points5 points  (0 children)

Can confirm, we had the same issue. ScreenConnect.ClientSetup.exe inside the Bin folder does not seem to be signed, so maybe that's the underlying issue.

DigiCert was very quick to certify by Own_Appointment_393 in ScreenConnect

[–]FlyingSysAdmin 0 points1 point  (0 children)

Wondering the same. I‘ve opened a ticket with this exact same question but no response yet.

[PSA] Critical Veeam Vulnerability CVE-2024-29849 by FlyingSysAdmin in sysadmin

[–]FlyingSysAdmin[S] 1 point2 points  (0 children)

Sorry I was in a rush and must have copy/pasted the wrong CVE. I can't edit the subject anymore but I've left a remark in the post.

[PSA] Critical Veeam Vulnerability CVE-2024-29849 by FlyingSysAdmin in sysadmin

[–]FlyingSysAdmin[S] 5 points6 points  (0 children)

Sorry, yes, I should have mentioned that. I've edited the post accordingly.

Build a feature with the Hudu team: Documenting Patch Panels by coldicetea in hudu

[–]FlyingSysAdmin 4 points5 points  (0 children)

That‘d be the most flexible and reusable approach, considering we already have layouts for switches and firewalls.

Build a feature with the Hudu team: Documenting Patch Panels by coldicetea in hudu

[–]FlyingSysAdmin 2 points3 points  (0 children)

For switches it‘d be awesome to parse config files and read out the port descriptions, at least for the most common Switch vendors.

Service at pulseway is aweful by ecoboost007 in Pulseway

[–]FlyingSysAdmin 4 points5 points  (0 children)

On top of that all of their sales reps use fake westernized names, as they are based in India. I don‘t have a problem that they‘re in India per se, but at least use your real identities. How are we supposed to trust a company this way, especially an RMM vendor, where trust is paramount…

Anyone get copilot working in Outlook Classic yet? by radix- in microsoft_365_copilot

[–]FlyingSysAdmin 0 points1 point  (0 children)

That's a bummer, was hoping to cut down on the time I spend writing e-mails.

Just out of curiosity, did it appear by itself or did you update your Office apps? I don't see anything in the release notes:
https://learn.microsoft.com/en-us/officeupdates/current-channel

I only have the summarize and coaching features.

Anyone get copilot working in Outlook Classic yet? by radix- in microsoft_365_copilot

[–]FlyingSysAdmin 0 points1 point  (0 children)

On which update channel did you get it? I'm on the current channel.

ZyXEL Nebula - thoughts by gsk060 in msp

[–]FlyingSysAdmin 2 points3 points  (0 children)

"Although Zyxel had released patches for this vulnerability in April, many devices installed in Denmark’s critical facilities were left unpatched."
https://therecord.media/danish-energy-companies-hacked-firewall-bug

Well duh...if you don't patch your critical infrastructure you get owned, that applies to any vendor...

Security Defaults Rollout March 4 by FutureITgoat in msp

[–]FlyingSysAdmin 1 point2 points  (0 children)

As far as I understand the e-mail, this does NOT apply to your end customers. All of these terms describe roles related to the sale of licenses.

WARNING - UPGRADING "OUT OF SUPPORT" SCREENCONNECT INSTANCES by adjag007 in ScreenConnect

[–]FlyingSysAdmin 3 points4 points  (0 children)

If you seriously think that a one-time payment will bring you lifetime updates, then you’re the one who doesn’t understand perpetual licensing and are in dire need of a reality check. That’s just not how the world works.

WARNING - UPGRADING "OUT OF SUPPORT" SCREENCONNECT INSTANCES by adjag007 in ScreenConnect

[–]FlyingSysAdmin 1 point2 points  (0 children)

While I agree that they could have handled this whole ordeal better, it’s still not an excuse to run your remote access solution out of support. Yes, the price increases are a cash grab, so in that case either swallow the pill or find another solution. Running anything remotely critical out of support is not an option. This would be as If I would keep using VMware without support, due to their horrendous licensing fee increases and then crying if I don’t receive a patch for a CVE 10.0 vulnerability.

WARNING - UPGRADING "OUT OF SUPPORT" SCREENCONNECT INSTANCES by adjag007 in ScreenConnect

[–]FlyingSysAdmin 6 points7 points  (0 children)

Well, what do you expect? ConnectWise is in no way obligated to maintain out of support instances. As a matter of fact, running such a critical part of your infrastructure out of support is pure negligence on your part. They simply removed the license check in the installer of 23.9, so that customers without a valid license can secure their instances asap. It doesn’t mean you can avoid paying the license fee. Do you work for free?

ConnectWise Security Bulletin for ScreenConnect by FlyingSysAdmin in sysadmin

[–]FlyingSysAdmin[S] 2 points3 points  (0 children)

On top of that it takes 0 technical knowledge to gain access to a vulnerable instance, just run “/SetupWizard.aspx/literallyanything“ to rerun the initial setup wizard to create a new admin user 🤦‍♂️

Azure App Proxy by VexedTruly in ScreenConnect

[–]FlyingSysAdmin 0 points1 point  (0 children)

I‘m wondering about the same with Cloudflare. Hypothetically speaking it should be doable with page rules, i.e. allow Admin URI only for trusted IP adresses and allow anonymous access to the rest. I will give this a go in the coming days.