Enter any website URL to analyze its complete technology stack

Executive Summary for www.niallbrady.com

1836 Response Time (ms)
200 HTTP Status
17 Scripts
13 Images
9 Links
HTTP/1.1 Protocol

SEO & Content Analysis

Basic Information
Page Title
just another windows noob ? | This is a blog by Niall C. Brady. Enterprise Mobility MVP.
Meta Description
Not detected
HTML Language
en-US
Robots.txt Present
Sitemap Present
total_urls: 5
SEO Meta Tags
content-type: text/html; charset=UTF-8
Page Content
just another windows noob ?IntroductionI started my day as always and launched the Windows app, I clicked my Cloud PC, entered my credentials and after a short delay I got an error shown below.The error shown above was “something went wrong” with a very not useful error code, -895352830. I tried this on multiple tenants with the same error code being generated.I asked Copilot what this meant and got the following detailsThis code corresponds to an AADSTS65002 token/permission issue during authentication.Microsoft documentation shows the same error pattern:Error: -895352830 (0xCAA20002) — occurs when a Microsoft first‑party app is missing required preauthorized API consent, causing token broker authentication to fail.[learn.microsoft.com]This means the Windows App cannot obtain a valid authentication token due to a Microsoft Entra (Azure AD) app permission issue, often triggered by:Broken SSO token brokerA corrupted local identity cacheA bad Windows Update interfering with Windows App authenticationThe last point above (a bad Windows Update) is indeed the cause.  More details below:January 2026 security patches (notably KB5074109) are currently breaking logins in the Windows App and Remote Desktop authentication:Microsoft confirms widespread credential failures after the January 2026 update, impacting Windows App sign-ins for Azure Virtual Desktop & Windows 365.[theregister.com]Users report the app immediately fails with authentication errors after pressing Connect.[theregister.com]Removing KB5074109 restores normal Windows App login functionality (confirmed by multiple users on Jan 15–16, 2026).[learn.microsoft.com]According to theregister.comThe upshot is that connecting to Windows 365 or Azure Virtual Desktop from the Windows App could be borked due to credential problems. Microsoft posted: “Investigation and debugging are ongoing, with coordination between Azure Virtual Desktop and Windows Update teams.”The problem is widespread and appears to affect every supported version of Windows, from Windows 10 Enterprise LTSC 2016, right up to Windows 11 25H2. Windows Servers 2019 to 2025 are also affected.Great, so now what ?Suggested workarounds are that you can connect to your Cloud PC using the soon to be unsupported Remote Desktop Client Agent available from here.I tried it, but it too failed to connect.Next, I tried via a web-browser, but that also didn’t work. The Cloud PC I’m trying to connect to is protected using the new CKIO feature and the web browser version does not support that.Verifying the problemA quick look in Intune, revealed that indeed the problematic CU was indeed applied to my Cloud PC’s and the PC I was making the connection from (Windows 11 25H2 ARMx64).Here’s a sample. As you can see belowBelow you can see the CU details…10.0.26200.762310.0.26100.7623https://support.microsoft.com/en-us/topic/january-13-2026-kb5074109-os-builds-26200-7623-and-26100-7623-3ec427dd-6fc4-4c32-a471-83504dd081cband within that you can see the known issues including the suggested workaround, which is to install KB5077744.As it’s so new this update is not even available in Windows Autopatch so you cannot currently use expedite updates policy to deploy this.KB5077744 is an Out‑of‑Band (OOB) update for Windows 11 25H2/24H2.It is not delivered through Windows Update automatically and must be manually downloaded and installed from the Microsoft Update Catalog.You must use the Microsoft Update Catalog to obtain the standalone package (MSU). [support.mi…rosoft.com]The fixAs KB5077744 is only currently available (at the time of writing, 2026/01/19) via Microsoft’s Catalog, you must deploy it (the msu) from Intune by wrapping it as a Win32 app.Because Intune does not directly deploy .MSU updates as updates, the supported method is to wrap the MSU as a Win32 app and deploy it to your affected clients.Go to Microsoft Update Catalog and search for kb5077744.Download the update that is applicable to your Windows OS version. Be aware that the file size is big, my download was approx 3.6GB.Place the downloaded msu file and this Powershell script in a folder called KB5077744.here’s the contents of the Powershell script, modify it so that it has the exact file name of the msu file you downloaded otherwise it won’t install. Save the file as Install_KB5077744.ps1.wusa.exe windows11.0-kb5077744-x64_fb63f62e4846b81b064c3515d7aff46c9d6d50c8.msu /quiet /forcerestart exit $LASTEXITCODENote: If you want to control reboot notifications and other options, package this instead using Powershell Application Deployment Toolkit and customize those options as necessary.Using Intunewinapputil.exe wrap the package as a Win32 app.Then add the Win32 appuse this command linepowershell.exe -ExecutionPolicy Bypass -File Install_KB5077744.ps1and the following detection script.$sysinfo = systeminfo.exe $result = $sysinfo -match "KB5077744" if ($result) { Write-Output "Found KB5077744" exit 0 } else { Write-Output "KB5077744 not found" exit 1 }Finally, after deploying the update to your affected clients, and waiting for it to install and restart, you’ll be able to connect again.Phew.What a relief.The new Windows build number is highlighted below.10.0.26200.7627 from a Windows 11 25H2 Cloud PC.and here you can see it successfully installed on the clientand of course, via Intune, however Intune still has not yet updated the build number of the CPC yet in the Win32 app install status.UpdateMake sure you patch the host PC making the connection to the Cloud PC and the Cloud PC if it has the .7623 patch level (January update). Also make sure to restart the patched computer at least twice.Related reading;

Network & Infrastructure

DNS & Hosting
IP Address
95.211.218.10
Reverse DNS
Not detected
SSL/TLS Certificate
Issuer
CN=R13, O=Let's Encrypt, C=US
Protocol Tls13
Expires In 48 days

Technology Stack

Content Management Systems
WordPress WordPress (robots.txt)
JavaScript Frameworks
jQuery
Build Tools
Rollup
Server Technologies
Generator: WordPress 6.9 PHP (inferred from WordPress)

Services & Integrations

Analytics & Tracking
Google Analytics GA4
Advertising & Marketing
Google AdSense
E-commerce Platforms
PrestaShop
Email Marketing
SendGrid

CDN & Media Providers

CDN Providers
cdnjs Cloudflare

Dynamic Analysis & Security

Dynamic JavaScript Analysis
Bootstrap (CSS Classes) CDNJS (script CDN) Cloudflare (script CDN) ES6+ JavaScript Features jQuery (CDN Detection) jQuery (Script Analysis) jQuery (script Resource) React (Script Analysis) Web Server: Apache
Server Headers
Apache

Resource Analysis

External Resource Hosts
cdnjs.cloudflare.com
gmpg.org
pagead2.googlesyndication.com
www.niallbrady.com
UI Frameworks & Libraries
Angular Material (Class Names) Bootstrap (Class Names) Vuetify (Class Names)

Social Media Integrations

Analysis Errors

Analysis Warnings & Errors
The following issues occurred during analysis:
  • Reverse DNS failed: No such host is known.
Analysis Complete

Analyzed www.niallbrady.com with 5 technologies detected across 10 categories

Analysis completed in 1836 ms • 2026-03-23 09:29:31 UTC