T O P

Powershell One-liner to Check Log Files

Troubleshooting Windows Update with a Little PowerShell Magic

Let’s suppose you’ve just joined a computer to a WSUS server, but Windows Update has decided it doesn’t feel like downloading patches today.

Naturally, your first instinct is to check the logs. But who wants to spend their afternoon digging through files looking for an error?

Fortunately, PowerShell can do the dirty work for us.

Back in the day, Windows Update maintained a nice, readable log file. Finding warnings was as simple as:

Get-ChildItem C:\Windows -Filter '*update*.log' -File -Recurse -ErrorAction SilentlyContinue |
    Select-String 'warning'

One line, and PowerShell searches for matching log files, reads their contents, and displays anything containing the word “warning.”

In my case, the result was rather revealing:

WARNING: Failed to find updates with error code 800B0001
WARNING: Digital Signatures are not trusted: Error 0x800b0001
WARNING: SelfUpdate check failed, error = 0x800B0001
WARNING: Skipping scan, self-update check returned 0x800B0001

Aha! There’s our culprit: 0x800B0001, pointing toward a digital signature verification issue.

But wait, it’s not 2013 anymore!

Modern Windows versions (Windows 10, Windows 11, and newer Windows Server releases) no longer maintain the same continuously updated text log. Instead, they use Event Tracing for Windows (ETW).

Not quite as convenient, but PowerShell still has our backs.

First, generate a readable log:

Get-WindowsUpdateLog -LogPath "$env:TEMP\WindowsUpdate.log"

Then search it:

Select-String "$env:TEMP\WindowsUpdate.log" -Pattern 'warning','error','failed'

Or, if you’re feeling particularly efficient, skip the log file altogether and query the Windows Update event log:

Get-WinEvent -FilterHashtable @{
    LogName = 'Microsoft-Windows-WindowsUpdateClient/Operational'
    Level = 2,3
} -MaxEvents 20 | Select-Object TimeCreated, Message

That retrieves up to 20 recent error and warning events, without opening Event Viewer.

And yes, these approaches work with Windows PowerShell 5.1 and modern PowerShell 7 versions.

One last trick

For traditional text logs that are actively being written, you can still watch for errors in real time:

Get-Content C:\Logs\Application.log -Tail 20 -Wait |
    Select-String 'warning','error'

Just remember that this trick doesn’t work directly with modern Windows Update’s binary ETW traces.

The moral of the story?

Windows Update may have changed how it keeps its secrets, but PowerShell is still remarkably good at getting them out.

Happy troubleshooting!

Fix! Portainer Published Ports Points to 0.0.0.0

I found this one today! In our Portainer instance, our Docker images and stacks that have external ports all point to 0.0.0.0:[port]. When you click on it, it goes nowhere (of course).

The fix? In the menu on the left, select Environment-related and then Environments. Select the environment you’re working with, and in the main window where it asks for Public IP put the IP of the host (192.168.x.x, etc.).

Okta Verify Delay or Loop on VPN?

We are finally moving towards implementing Okta FastPass in our Okta Identity Engine environment and have begun testing internally. A very early bug we have encountered is that when on our “VPN” (Twingate), the prompt for authentication hangs and takes several seconds to happen.

Digging through Okta Verify logs on the device yielded nothing and after searching around and searching deeper, I found an article on Okta’s support site that yielded the answer – we need to whitelist the domain authenticatorlocalprod.com in our VPN, specifically because that domain gets flagged in the DNS Rebind feature. Once we whitelisted the domain, Okta Verify prompts came through immediately.

Getting Started with Google Gemini

We’ve begun rolling out Gemini and it’s been moving quickly in terms of updates and rollout. Here are our current settings that are letting users use it. Make sure your legal and compliance teams approve first!

Apps

User Access

Make sure you have a Gemini license, or your data may be used to train models

Service Status

Turn it on for OUs or just groups

Google Groups – Emails are Bouncing

I’ve encountered this error in a few circumstances – users in Google Groups will have a red triangle and the text “Emails are Bouncing” that stops them from receiving any Google Group emails – definitely not good! I’ve seen this when former employees’ accounts are deactivated but not removed from Google Groups and then re-hired or activated later.

The fix is either remove and re-add them to their Google Group via GAM OR to have the employee go to groups.google.com, click the gear icon in the upper right, and click Global Settings.

From there, they should see under “Bounce Status” that their email is flagged as bouncing and a link that says “Resend request to recheck status” or something like that. After that, they’ll see a message that says “your email is not flagged as bouncing”. That’s it!