5G, Mobile

5G Beyond the Label — What You Need to Know Before Buying a 5G Phone

Leave a comment

5G Beyond the Label — What You Need to Know Before Buying a 5G Phone

In today’s mobile market, nearly every phone claims to support 5G. But does that mean they all deliver the same speed and performance?

Not at all.

Let’s break down the truth behind the label — so you can make an informed decision before your next phone purchase.

📊 Real-World 5G Speed Comparison

Phone TypeTypical 5G Download Speed
Flagship Phones (e.g., iPhone 15 Pro, Galaxy S23)400–900 Mbps
Mid-Range Phones (e.g., Pixel 6a, Galaxy A54)150–400 Mbps
Budget Phones (entry-level 5G models)60–150 Mbps

🔍 Why 5G Performance Varies by Phone

FactorImpact
Modem TypePhones with advanced 5G modems (like Qualcomm X70 or MediaTek M80) offer faster speeds and better signal handling.
5G Bands SupportedPhones with mmWave support offer ultra-fast speeds; sub-6GHz is slower but has wider coverage.
Carrier AggregationPremium phones combine multiple signals for better performance.
Thermal DesignBetter cooling systems prevent speed drops during heavy use.
Network ConditionsYour mobile provider’s 5G rollout and tower proximity affect real-world speeds.

🛡️ Kapothi’s Advice

Don’t choose a phone just because it says “5G.”
Choose one that’s built to deliver real speed, stable connectivity, and future-ready performance.

🌀 Closing Thoughts

At Kapothi, we believe in truthful tech guidance.
This post is part of our commitment to helping clients, elders, and entrepreneurs make smart, confident decisions — whether it’s choosing a phone, securing autofill, or building resilient infrastructure.

Microsoft Windows, Windows 11

With Windows 11 version 25H2, Microsoft has officially ended support for 32-bit (x86) processors

Leave a comment

🛑 Farewell to x86: Windows 11 25H2 Marks the End of 32-Bit Support

With the release of Windows 11 version 25H2, Microsoft has officially retired support for 32-bit (x86) processors, closing a chapter that began nearly four decades ago.

This architectural shift means that new installations of Windows 11 will require 64-bit (x64 or ARM64) processors. Devices running legacy x86 hardware will no longer be eligible for upgrades, signaling a clear move toward modern, secure, and performance-optimized computing.

🧠 Why This Matters

  • x86 architecture, once the backbone of personal computing, is limited to ~4 GB of RAM and narrower CPU registers.
  • x64 systems, by contrast, can theoretically address up to 18.4 million TB of memory, enabling richer multitasking, virtualization, and security features.
  • Microsoft’s decision aligns with industry trends — most operating systems, apps, and hardware vendors have already phased out 32-bit support.

🌀 What It Means for You

  • If your device runs on x64 hardware, the transition is seamless — 25H2 arrives as a lightweight enablement package.
  • If you still rely on x86 systems, it’s time to plan your upgrade path. While older versions of Windows may continue to function, they’ll no longer receive the latest features or security updates.

📜 Editorial Note

At KAPOTHI, we see this not as an end, but as a ritualized evolution — a farewell to legacy constraints and a step toward sovereign computing. Whether you’re an archivist of old machines or a builder of future infrastructure, this moment deserves to be remembered.

“Legacy dissolves. Architecture evolves. 25H2 marks the silent farewell.”

Windows Defender

🛡️ Windows Defender Management Commands

Leave a comment

🛡️ Windows Defender Management Commands

✅ Check if Defender is Running

PowerShell Get-Service -Name WinDefend

📅 Check Last Update Time

PowerShell Get-MpComputerStatus | Select-Object AntivirusSignatureLastUpdated

🔄 Force Update Definitions

PowerShell Update-MpSignature

🧠 Check Overall Defender Status

PowerShell Get-MpComputerStatus

🚀 Run a Quick Scan

PowerShell Start-MpScan -ScanType QuickScan

🧹 Run a Full Scan

PowerShell Start-MpScan -ScanType FullScan

📂 Exclude a Folder

PowerShell Add-MpPreference -ExclusionPath “C:\Your\Folder\Path”

📄 Exclude a File

PowerShell Add-MpPreference -ExclusionProcess “C:\Your\Folder\app.exe”

🧩 Exclude a File Extension

PowerShell Add-MpPreference -ExclusionExtension “.log”

❌ Remove Folder Exclusion

PowerShell Remove-MpPreference -ExclusionPath “C:\Your\Folder\Path”

📋 View All Exclusions

PowerShell Get-MpPreference | Select-Object -ExpandProperty Exclusion*

⏸️ Disable Real-Time Protection

PowerShell Set-MpPreference -DisableRealtimeMonitoring $true

▶️ Re-enable Real-Time Protection

PowerShell Set-MpPreference -DisableRealtimeMonitoring $false

🛡️ Enable Defender Tray Icon on Windows Server

PowerShell Set-MpPreference -UILockdown $false

🧠 Registry Tweak (Optional)

Registry Path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\UX Configuration
DWORD Value Notification_Systray = 1

After applying these, restart or log off to see the Defender shield icon in your system tray. This works on Windows Server 2016, 2019, and 2022.

🧭 Force Update via CMD

Command Prompt “%ProgramFiles%\Windows Defender\MpCmdRun.exe” -SignatureUpdate

🧭 Run Quick Scan via CMD

Command Prompt “%ProgramFiles%\Windows Defender\MpCmdRun.exe” -Scan -ScanType 1

🧭 Run Full Scan via CMD

Command Prompt “%ProgramFiles%\Windows Defender\MpCmdRun.exe” -Scan -ScanType 2

These commands help you ritualize Defender’s vigilance—ensuring your server remains clean, updated, and ready to archive without interruption.

Microsoft Windows, PowerShell

Guide: Find the Real Windows Process Behind a PID

Here’s a precise worthy guide to help you identify which Windows process is truly using a specific PID (Process ID)

🔍 1. Use Task Manager (Quick View)

  • Press Ctrl + Shift + Esc to open Task Manager.
  • Go to Details tab.
  • Locate the PID column (enable it via right-click on column headers if hidden).
  • Match your target PID to its Image Name (e.g., svchost.exe, chrome.exe).

⚠️ This shows the process name, but not the full command line or parent-child relationships.

🧰 2. Use Command Line (Precise & Scriptable)

A. Find Process by PID

tasklist /FI "PID eq 1234"

Replace 1234 with your actual PID.

B. Get Full Command Line

wmic process where processid=1234 get Caption,Commandline

C. Get Parent Process

wmic process where processid=1234 get ParentProcessId

Then:

tasklist /FI "PID eq <ParentPID>"

🧪 3. Use PowerShell (Editorial Precision)

A. Get Process Info

Get-Process -Id 1234 | Select-Object Name,Id,Path

B. Full Command Line

Get-CimInstance Win32_Process -Filter "ProcessId = 1234" | Select-Object CommandLine

C. Parent Process

(Get-CimInstance Win32_Process -Filter "ProcessId = 1234").ParentProcessId

🧠 4. Use Process Explorer (GUI + Deep Insight)

  • Download from Microsoft Sysinternals.
  • Launch as Administrator.
  • Press Ctrl + F and enter the PID.
  • View full tree, command line, DLLs, handles, and parent-child lineage.

Server

How to Install Remote Desktop Session Host on a Standalone Windows Server (Workgroup Mode)

Leave a comment

This guide walks you through installing and configuring Remote Desktop Session Host (RDSH) on a standalone Windows Server—no domain join required. Perfect for labs, sovereign setups, or lightweight deployments.

✅ Step 1: Install RDS Roles via PowerShell

Open PowerShell as Administrator and run:

Install-WindowsFeature -Name RDS-RD-Server, RDS-Licensing -IncludeManagementTools
Restart-Computer

This installs:

  • Remote Desktop Session Host
  • Remote Desktop Licensing

✅ Step 2: Create Licensing Registry Key

After reboot, create the missing registry path:

New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server" -Name "Licensing Core" -Force
Continue reading How to Install Remote Desktop Session Host on a Standalone Windows Server (Workgroup Mode) →
Windows 11

Windows 11 25H2: The Vanishing Local Account and the Rise of Cloud-Only Identity

Leave a comment

and yes, Windows 11 version 25H2 does make it harder to create local accounts, especially during setup. But here’s the twist: it’s still possible, just not obvious.

What Microsoft Changed

  • In 25H2, Microsoft enforces Microsoft account sign-in during installation for most editions (Home, Pro)
  • The usual tricks like entering a fake email or skipping Wi-Fi no longer work reliably
  • This is part of their push toward cloud-connected experiences, syncing, and telemetry

🛠️ How You Can Still Create a Local Account in Windows 11 25H2

Microsoft enforces Microsoft account sign-in during setup, but there are still hidden ways to create a local account. These are unofficial workarounds and may change in future builds.

🔹 Command Prompt Trick

Use this hidden command during setup:

Command Prompt # On the setup screen, press Shift + F10
start ms-cxh:localonly

This launches a hidden flow that lets you create a local account without needing a Microsoft login.

🔹 Registry Hack (if needed)

If the above fails, you can add a registry key to bypass the requirement:

Command Prompt reg add “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE” /v BypassNRO /t REG_DWORD /d 1 /f

Restart setup after adding this key, and you’ll be able to create a local account.

🌐 Cloud vs Local Identity in Windows 11

Microsoft is moving toward cloud-only identity, but local accounts still matter for sovereignty and control. Here’s a clear comparison:

☁️ Cloud Identity (Microsoft Account / Entra ID)

Pros • Easy password recovery
• Syncs settings, files, and apps across devices
• Integrated with OneDrive, Outlook, Microsoft Store
• Required for some features (Copilot, Widgets, Teams)
Cons • Requires internet during setup
• More telemetry and data sharing
• Less control for offline or sovereign setups
• Dependency on Microsoft ecosystem

🖥️ Local Identity (Traditional Local Account)

Pros • Works fully offline
• Greater privacy and sovereignty
• No dependency on Microsoft services
• Ideal for test labs, archival machines, or secure setups
Cons • Harder to set up in 25H2
• No automatic sync or recovery
• Some features disabled or hidden
• Requires manual backups and updates

⚖️ Bottom line: Cloud identity offers convenience and integration, while local identity preserves sovereignty and offline control. Choose based on your needs.

⚠️ Important Note

These methods are unofficial and may stop working in future updates. They are best used for testing, offline machines, or sovereign setups where cloud identity is not desired.

Other

“Starlink in Sri Lanka: Key Questions I Asked Gemini”

Leave a comment

“Do people in the U.S. choose to buy Starlink instead of using their existing home internet services, or do most stick with what they already have because it’s fast and reliable enough? Is Starlink mainly popular among those living in remote or underserved areas?”

That’s an insightful question and gets to the core of Starlink’s business model and target market in a place like the United States.

You are correct: the vast majority of people in the USA who buy Starlink are those in rural or remote areas where traditional internet options are either non-existent or extremely poor.

Here’s why Starlink isn’t a widespread competitor to fiber and cable internet in urban and suburban areas:

Continue reading “Starlink in Sri Lanka: Key Questions I Asked Gemini” →
Microsoft Windows

Global Outage Alert: Windows BSOD Crisis Following CrowdStrike Update – Recovery Steps

Leave a comment

Table of Contents

Official CrowdStrike post | https://www.crowdstrike.com/blog/technical-details-on-todays-outage/
Source | https://blog.qualys.com/

  • Steps For Regaining Access to Windows PCs, AWS & Azure
  • Qualys Assurance No Impact on Our Services

On Friday, July 19, 2024, morning, reports surfaced globally of Microsoft Windows operating system users encountering the infamous Blue Screen of Death (BSOD) following the latest update from CrowdStrike. This widespread issue has severely impacted critical services, including telecommunications, banking, airline and railway operations, supermarkets, hospitals, and major news networks.

Steps For Regaining Access to Windows PCs, AWS & Azure 

CrowdStrike has outlined a four-step process for regaining access to Windows PCs affected by the update:

  1. Boot Windows into Safe Mode or the Windows Recovery Environment.
  2. Navigate to the C:\Windows\System32\drivers\CrowdStrike directory.
  3. Locate and delete the file matching “C-00000291*.sys”.
  4. Boot the host normally.

For cloud environments, customers can revert to a snapshot taken before 4:09 am UTC.

For AWS (Amazon Web Services), follow these steps:

  1. Detach the EBS volume from the impacted EC2 instance.
  2. Attach the EBS volume to a new EC2 instance.
  3. Fix the CrowdStrike driver folder.
  4. Detach the EBS volume from the new EC2 instance.
  5. Attach the EBS volume back to the impacted EC2 instance.

For Azure, follow these steps:

  1. Log in to the Azure console. 
  2. Go to Virtual Machines and select the affected VM. 
  3. In the upper left of the console, click “Connect”. 
  4. Click “More ways to Connect” and then select “Serial Console”. 
  5. Once SAC has loaded, type in ‘cmd’ and press Enter. 
  6. Type ‘ch -si 1’ and press the space bar. 
  7. Enter Administrator credentials. 
  8. Type the following commands:
    • ‘bcdedit /set {current} safeboot minimal’ 
    • ‘bcdedit /set {current} safeboot network’ 
  9. Restart the VM. 
  10. To confirm the boot state, run the command: ‘wmic COMPUTERSYSTEM GET BootupState’. 

The manual nature of this fix poses a significant challenge for companies, especially those without backups for all VDIs, potentially slowing down the recovery process. Customers will also need a recovery key to access Safe Mode if Bitlocker is enabled on the system disk. 

CrowdStrike Engineering has reversed the changes causing this issue, with the error code displayed on affected systems: “Tech-Alert-Windows-crashes-related-to-Falcon-Sensor-2024-07-19.“

Source | https://blog.qualys.com/vulnerabilities-threat-research/2024/07/19/global-outage-alert-windows-bsod-crisis-following-crowdstrike-update-recovery-steps-qualys-assurance

Windows Server 2022

KB5034439: Windows Recovery Environment update for Windows Server 2022: January 9, 2024 | Error message:  0x80070643

Leave a comment

Source | Microsoft https://support.microsoft.com/en-us/topic/kb5034439-windows-recovery-environment-update-for-windows-server-2022-january-9-2024-6f9d26e6-784c-4503-a3c6-0beedda443ca

Recommended methods available at

To avoid this error or recover from this failure, please follow the Instructions to manually resize your partition to install the WinRE update and then try installing this update.

Or, to use a sample script to increase the size of the WinRE recovery partition, see Extend the Windows RE Partition.

Windows Server 2022

Summary

This update automatically applies Safe OS Dynamic Update (KB5034235) to the Windows Recovery Environment (WinRE) on a running PC to address a security vulnerability that could allow attackers to bypass BitLocker encryption by using WinRE. For more information, see CVE-2024-20666.

NOTE If your running PC does not have a WinRE recovery partition, you do not need this update. To verify if you have WinRE enabled, you can run the following command in an elevated command prompt: reagentc /info

If WinRE is enabled you will see Windows RE status in the output with a value of Enabled.

IMPORTANT This update requires 250 MB of free space in the recovery partition to install successfully. If the recovery partition does not have sufficient free space, this update will fail. In this case, you will receive the following error message:  0x80070643 – ERROR_INSTALL_FAILURE  To avoid this error or recover from this failure, please follow the Instructions to manually resize your partition to install the WinRE update and then try installing this update. Or, to use a sample script to increase the size of the WinRE recovery partition, see Extend the Windows RE Partition.