A surprisingly large C:\Windows\System32\Configuration folder can consume tens of gigabytes on a Windows Server. One common cause is the DSC (Desired State Configuration) status history stored in the ConfigurationStatus folder.
In this case, the folder contained more than 30,000 status files and consumed over 40 GB of disk space. Although the Local Configuration Manager (LCM) was configured to retain status information for only a limited number of days, old files were still present, indicating that the cleanup process was no longer working correctly.
A structured approach helps determine whether the problem is caused by excessive status files, corrupted DSC state information, or a failing configuration.
The process consists of three main steps:
Following these steps helps reclaim disk space, restore DSC functionality, and identify configuration issues that may prevent DSC from running successfully.
If cleanup does not resolve the issue, the next step is to investigate DSC itself.
First restart the relevant services:
Restart-Service WinRM -Force
Restart-Service WmiApSrv -Force -ErrorAction SilentlyContinueNext, review the DSC operational log for detailed error messages:
Get-WinEvent -LogName "Microsoft-Windows-DSC/Operational" -MaxEvents 20 |
Select-Object TimeCreated, Id, LevelDisplayName, Message |
Format-ListThe operational log often reveals the resource responsible for the failure.
To test the current DSC configuration, manually start a configuration run:
Start-DscConfiguration -UseExisting -Wait -VerboseIn this scenario, DSC reported a failure in the MSFT_AccountPolicy resource while attempting to update the Minimum_Password_Length setting.
This indicates that:
At this stage, review the DSC configuration source and verify whether password policy settings should still be managed by DSC. Correcting or removing the failing configuration and then applying a new configuration is typically the final step in restoring a healthy DSC environment.
Once the folder size is known, inspect how DSC is configured and whether it should be removing old status records.
Check the types of files stored in the status folder:
Get-ChildItem "C:\Windows\System32\Configuration\ConfigurationStatus" |
Group-Object Extension |
Sort-Object Count -Descending |
Select-Object Count, NameThis provides insight into what DSC is generating and whether unexpected file types are present.
Review the Local Configuration Manager (LCM) configuration:
Get-DscLocalConfigurationManager | Select-Object *Pay particular attention to:
| Setting | Purpose |
|---|---|
| ConfigurationMode | Defines how DSC applies configurations |
| RefreshMode | Determines how configurations are received |
| StatusRetentionTimeInDays | Controls how long status history is kept |
| RefreshFrequencyMins | Defines how often DSC checks for updates |
Finally, inspect the recorded DSC execution history:
Get-DscConfigurationStatus -AllIf DSC reports deserialization errors, the status history or DSC state information may be corrupted and additional repair steps will be required.
The ConfigurationStatus folder contains historical DSC execution information. When retention stops working correctly, the folder can grow to many gigabytes and contain thousands of old files.
Before deleting anything, stop the WinRM service and create a backup location:
Stop-Service WinRM
New-Item D:\DSCBackup -ItemType DirectoryA practical approach is to remove status files older than 30 days:
Get-ChildItem "C:\Windows\System32\Configuration\ConfigurationStatus" |
Where-Object LastWriteTime -lt (Get-Date).AddDays(-30) |
Remove-Item -ForceThis removes only historical status information and leaves recent records intact.
After the cleanup, verify whether DSC can read the remaining status information:
Get-DscConfigurationStatus | Select-Object StartDate,Type,StatusIf DSC status retrieval works again, the problem was likely caused by old or corrupted status files.
If the same deserialization error continues to appear even after removing the historical data, the issue is likely deeper than the status history itself and may involve corrupted DSC state information or a failing DSC configuration.
Cleaning the folder reduces disk usage, but additional troubleshooting may still be necessary to restore full DSC functionality.
A large ConfigurationStatus folder is often the first sign that DSC status retention is no longer working correctly. Before making any changes, determine how much space is being consumed and whether old status files are accumulating.
First identify the operating system version:
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumberThis helps determine whether known DSC issues may apply to the server version.
Count the number of status files:
(Get-ChildItem "C:\Windows\System32\Configuration\ConfigurationStatus").CountA very high number may indicate that status files are no longer being cleaned up automatically.
Calculate the total size:
Get-ChildItem "C:\Windows\System32\Configuration\ConfigurationStatus" -File |
Measure-Object Length -SumReview the oldest files:
Get-ChildItem "C:\Windows\System32\Configuration\ConfigurationStatus" |
Sort-Object LastWriteTime |
Select-Object -First 10Review the newest files:
Get-ChildItem "C:\Windows\System32\Configuration\ConfigurationStatus" |
Sort-Object LastWriteTime -Descending |
Select-Object -First 10Comparing old and new files helps determine whether retention is working and whether DSC is still actively generating status data.
Have you ever wondered where all your disk space has gone? Instead of manually browsing folders, Windows includes a powerful command that quickly identifies the largest space consumers on your drive.
diskusage C:\ /h /t=10This command scans the C: drive and displays the 10 largest folders or files, helping you quickly locate areas that consume the most storage.
| Option | Description |
|---|---|
C:\ |
Starts the scan at the root of the C: drive |
/h |
Shows sizes in a human-readable format (MB, GB, TB) |
/t=10 |
Limits the output to the top 10 largest results |
45.2 GB C:\Windows
32.8 GB C:\Users
18.4 GB C:\Program Files
12.1 GB C:\ProgramDataIn this example, the largest space consumers are displayed first, making it easy to focus cleanup efforts where they will have the biggest impact.
Show all results:
diskusage C:\ /hAnalyze a specific folder:
diskusage C:\Windows /h /t=20Limit the folder depth:
diskusage C:\ /h /u=3If a Windows machine is running low on disk space, this command is often one of the fastest ways to discover where the storage is being used.
Thinking about trying a newer version of Visual Studio without changing your current setup? Good news: different major versions of Visual Studio can be installed on the same computer and used independently.
How It Works
Visual Studio 2022 and Visual Studio 2026 are designed to support side-by-side installation. Installing the newer version does not replace or uninstall the older one. Each version maintains its own:
This makes it easy to test new features while continuing to work on existing projects in a stable environment.
Benefits
Things to Consider
Recommended Approach
Many developers keep the older version for day-to-day work and install the newer version for testing, learning, and evaluating new capabilities. This provides flexibility while reducing the risk of disrupting existing projects.
For most users, running both versions side by side is the safest and most practical way to evaluate a new Visual Studio release.
Email attacks are becoming smarter, faster, and harder to detect. In its latest security report, Microsoft revealed how phishing campaigns evolved during the first quarter of 2026 — and why traditional defenses are no longer enough.
Attackers are moving away from simple spam emails and using more advanced social engineering tactics. One of the biggest changes is the rapid growth of QR code phishing (sometimes called quishing). Instead of clicking suspicious links, users are tricked into scanning QR codes that lead to fake login pages. Microsoft reported that these attacks more than doubled during the quarter.
Another rising tactic is CAPTCHA-gated phishing, where fake verification steps make malicious websites appear trustworthy. These campaigns are designed to bypass automated security tools and create a false sense of legitimacy.
The report also highlighted the continued rise of Business Email Compromise (BEC) attacks. Rather than using malware, attackers impersonate coworkers, managers, or finance teams to request payments, payroll updates, or sensitive information.
Key lessons from the report:
The main takeaway: cybersecurity today is not only about blocking malware — it’s about protecting identities and recognizing manipulation before damage is done.
Original article: Microsoft Security Blog
Running code on a supercomputer sounds simple — until you see what happens behind the scenes. Modern high-performance machines are not just “big computers.” They are massive systems built from thousands of connected processors, advanced cooling systems, and highly optimized software.
The article explores the hidden complexity of running applications on a European supercomputer worth hundreds of millions of euros. Unlike a normal laptop or cloud server, these machines require developers to think differently about performance, memory usage, and communication between computing nodes.
Key challenges include:
One interesting takeaway is that writing code for supercomputers is often more about engineering and planning than raw programming skill. Developers must understand hardware architecture, networking, and scalability to fully use the machine’s power.
The article also highlights how these systems support scientific research, AI training, climate modeling, and complex simulations that would be impossible on consumer hardware.
Original article: What It Actually Takes to Run Code on a €200M Supercomputer
Artificial intelligence is changing how companies work — but what happens when employees themselves become part of the training data? A recent internal move at Meta has sparked debate about privacy, workplace culture, and the future of AI-powered organizations.
According to reports, Meta introduced software that monitors employee activity on company devices. The system can reportedly track actions such as mouse movements, clicks, typing behavior, and screenshots within approved work applications. The goal appears to be improving AI systems by studying how people interact with digital tools in real work environments.
This decision highlights a growing shift in the tech industry:
Critics argue that constant monitoring may damage trust between companies and workers. Others believe these systems could eventually improve productivity and help businesses automate repetitive tasks more effectively.
The situation also raises larger questions:
| Topic | Why It Matters |
|---|---|
| Workplace Privacy | Employees may worry about excessive monitoring |
| AI Training Data | Human behavior is becoming valuable input for AI |
| Company Culture | Trust and morale can be affected by surveillance tools |
As AI adoption accelerates, businesses will likely face growing pressure to balance innovation with employee rights and transparency.
Original article: TheStreet article