r/windowsdev • • Oct 23 '19

Hire windows developers

Thumbnail
posts.gle
0 Upvotes

r/windowsdev • • 13d ago

I made a free app that puts a tiny robot vacuum on your Windows desktop: click it, it eats the clutter, and it asks before anything goes

0 Upvotes

I got tired of my desktop turning into 60 screenshots and old installers that I never cleaned up, so I built Sweepy.

How it works: a little robot sits on a dock in the corner of your desktop. Click it, and it backs out, scans the desktop with a little lidar sweep, then drives lanes like a real robot vacuum and eats the clutter. When it's done it goes home and asks first: you see every file it picked up, untick anything you want to keep, and the rest goes to the Recycle Bin. "Undo last clean" brings it all back.

Right-click any folder (like Downloads) and pick "Bring Sweepy here" to clean that too, and there's a deep clean for leftovers from uninstalled apps, old temp files and crash dumps (it found 5 GB on my PC). You can grab it mid-clean (it gets dizzy), and if you right-click and stop it, it cries a little and drives home.

- Free for your desktop, forever. Pro is $6.99 once, no subscription (folders, deep clean, big files, schedules, every skin), with a 3-day free trial, no card

- Under 20 MB of memory and 0% CPU while it waits

- Never touches shortcuts, locked files or anything you changed in the last 10 minutes

- Everything runs on your PC, no account

- Microsoft Store: https://apps.microsoft.com/detail/9P31M4SCNXS5?cid=reddit

- Website: https://sweepy.essam.biz

I'd love feedback, especially on what it should never eat!


r/windowsdev • • Sep 06 '21

WSAStartup

0 Upvotes

Do others wish that Microsoft would get rid of the WSAStartup API in Windows 11?

The front tier of my code generator is 27 lines long. It could be 26 lines long if WSAStartup wasn't needed.


r/windowsdev • • Jan 25 '18

Building Widget Dashboard using UWP and Caliburn.Micro - Mikael Koskinen

Thumbnail
mikaelkoskinen.net
1 Upvotes

r/windowsdev • • Apr 17 '16

Visual C++ UWP: add Image to screen from cpp

0 Upvotes

Now in C#, for better usage of the UWP environment. This is now obsolete.

I want to add an image to the screen at a given location within the C++ code, not the XAML. So, when the user clicks a button, the image is created and shown. It has to be created on the spot.

//
// MainPage.xaml.cpp
// Implementation of the MainPage class.
//

#include "pch.h"
#include "MainPage.xaml.h"

using namespace Audi;

using namespace Platform;
using namespace Windows::Foundation;
using namespace Windows::Foundation::Collections;
using namespace Windows::UI::Xaml;
using namespace Windows::UI::Xaml::Controls;
using namespace Windows::UI::Xaml::Controls::Primitives;
using namespace Windows::UI::Xaml::Data;
using namespace Windows::UI::Xaml::Input;
using namespace Windows::UI::Xaml::Media;
using namespace Windows::UI::Xaml::Navigation;


MainPage::MainPage()
{
	InitializeComponent();
}


void Audi::MainPage::comboBox_SelectionChanged(Platform::Object^ sender Windows::UI::Xaml::Controls::SelectionChangedEventArgs^ e)
{

}

void Audi::MainPage::addObj(Platform::Object^ sender, Windows::UI::Xaml::RoutedEventArgs^ e)
{
	//create image here
}

r/windowsdev • • Jan 12 '16

Sending Image Data with parameter using HttpClient Post

Thumbnail
winplatform.wordpress.com
0 Upvotes

r/windowsdev • • Feb 18 '22

Deleted value in reg and now wont boot

0 Upvotes

I messed up.

My Intel driver didnt work so i went into reg (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class ) and deleted UpperFilters and LowerFilters for 4D36E972-E325-11CE-BFC1-08002BE10318 and now my computer wont go pass the boot screen. Not even in safe mode.

Think it might have messed with my boot drive. Its not showing. I turn CSM on and it shows but still doesnt boot


r/windowsdev • • Jun 04 '26

an idea I had :)

0 Upvotes

I got a very weird but interesting idea that I'd like to share with you all... you can find it here. it's about reviving the NT kernel agnostic environment subsystem system by making a custom environment subsystem that replaces win32 (CSRSS)
I'd like to hear your thoughts about it!

from a pure practical perspective, I don't really know any useful use case for it
but it's very exciting for me to work on just to understand windows internals + having fun with NT


r/windowsdev • • Mar 29 '20

Why is Win32 being stripped away and being replaced by UWP?

4 Upvotes

As a dev, I use Win32 mainly because it’s faster and more powerful than the lump of shit called UWP. My experience with UWP apps has been clunky and slow, but Win32 apps are fast, snappier, don’t take batshit insane times to open, and are generally more powerful on the technical side. Why is microsoft ridding away with Win32


r/windowsdev • • Jul 19 '26

I've been building a modern Windows cache cleaner called CachePilot – looking for honest feedback

Thumbnail
gallery
3 Upvotes

Hi everyone,

For the past few months I've been working on a desktop application called CachePilot.

The goal is simple: make cleaning Windows cache easy, safe, and understandable. Most existing cleaners either look outdated, are filled with ads, or delete files without explaining what they actually are.

Current progress

The application is built with:

  • Electron

  • React

  • TypeScript

  • Vite

So far I've implemented:

  • ✅ Real cache scanning (not fake progress bars)

  • ✅ One-click cleanup

  • ✅ Modern dark UI

  • ✅ System tray support

  • ✅ Scan history

  • ✅ Automatic scanning

  • ✅ Windows notifications

  • ✅ Clear explanations for every cache category before deleting anything

  • ✅ Local-first design (nothing is uploaded to a server)

What I'm still working on

  • Better scan performance

  • More cache locations

  • Better analytics and cleanup reports

  • Polish before the first public release

I'd love your feedback

I'm mainly trying to answer these questions:

  • Would you actually use an app like this?

  • What features are missing?

  • What do you dislike about current tools like CCleaner or Windows Disk Cleanup?

  • Would you pay for a lifetime license if it solved your problem?

If you'd like to try it:

📥 WebSite: https://mostafaarihani-debug.github.io/CachePilot/

📋 2-minute Survey: https://tally.so/r/Y5KPgv

I'm looking for completely honest feedback—even if it's negative. I'd rather improve the app now than launch something people don't actually want.

Thanks for taking the time to check it out!


r/windowsdev • • Sep 28 '25

What exactly is a Windows Handle ?

3 Upvotes

Im learning Windows programming and often see the word Handle (for example in CreateFile or OpenProcess) what exactly is a Handle inside Windows and why we need it ? A short example would really help me understand.


r/windowsdev • • Oct 17 '26

Tired of Windows updates breaking your PC? I built a traffic light for them

1 Upvotes

windows updates break stuff way too often (black screens, audio, remote desktop) and the dumb part is microsoft usually lists the problem publicly. nobody checks that before updating

so i made patchlight. it checks every pending update against microsoft's known issues and gives it a green / yellow / red light. red ones get paused automatically and come back once microsoft fixes them. everything else keeps installing

github.com/G4SBO/PatchLight

lmk what u think, any feedback is appreciated ;)


r/windowsdev • • Jan 05 '16

[Stacoverflow question] Icon overlays are showing blurry on "Large Icons"

Thumbnail
stackoverflow.com
1 Upvotes

r/windowsdev • • Apr 12 '24

FoxPro 2.6a for MS-DOS complete tutorial for beginners

Thumbnail
youtube.com
0 Upvotes

r/windowsdev • • Jan 22 '18

deanchalk/UWPChipsControl

Thumbnail
github.com
1 Upvotes

r/windowsdev • • Aug 03 '18

XAML Resouce Dictionary for Segoe MDL2 Assets · GitHub

Thumbnail
gist.github.com
1 Upvotes

r/windowsdev • • Apr 20 '17

Windows 10 UWP Game FooFoo Go! Run! Jump! For mobile, PC, HoloLens, Windows Mixed Reality, Surface Hub and eventually Xbox One this summer via Xbox Creators Program.

Thumbnail
microsoft.com
1 Upvotes

r/windowsdev • • Jul 03 '19

Is there any way to create password rest software for windows?

0 Upvotes

Hi Guys,

I need to know how to create windows password reset software is created and in which programming language can we create that password. Many Thanks in advance.


r/windowsdev • • May 02 '26

Observation: OS Build number No Longer Reliably Predicts Driver Success After HVCI Hardening

1 Upvotes

TL;DR / Observation:

After enabling Core Isolation (HVCI), older drivers (including UMDF 2.15) can become effectively incompatible on that machine — even when re-installing a previously working driver.

The long-standing practice of selecting driver packages based solely on Operating System version or build number is no longer sufficient.

Background:

I’ve been seeing seemingly random failures with modern drivers (especially biometric / WBF ones) on Windows 10 and 11. The same driver build works fine on one machine but fails on another with the identical OS version and build number. After extensive testing with HLK-validated drivers, I believe this is caused by per-machine hardening (Core Isolation / HVCI) that can make older UMDF 2.15 drivers inoperable after a 2.25+ driver has been installed.

This would appear to be a significant (and mostly undocumented) shift in how Windows handles driver compatibility.

This is not random behavior. Diagnostics on a post-Windows 10 targeted driver revealed a significant shift in Windows security enforcement. Testing and research indicate that this issue affects a growing range of drivers, particularly those using the Windows Biometric Framework (WBF) and modern UMDF components.

Addendum: Scope of the Hardening Effect While it may overstate the situation to call this a universal new paradigm across all Microsoft drivers, the practical effect for end users is very real. Many users deploy only a single specialized peripheral. When a modern driver triggers the hardening process — typically through UMDF 2.25+ components and HVCI enforcement — older drivers for that device can become inoperable on that specific machine.

Unless significant steps are taken to undo the triggering event (which is rarely practical or reliable), the affected device will no longer function. From the user’s perspective, both the peripheral and the associated software appear to have failed.

This customer-level reality — not the broader industry average — is the operational context that must be addressed.

  1. Working It Out (The Diagnostic Proof)

Testing was conducted to validate backward compatibility from a Windows 11-targeted driver down to Windows 10. The peripheral used was a biometric fingerprint reader. The drivers tested included HLK-validated and Microsoft-signed packages targeting Windows 10 (Release 17763) and Windows 11 driver containing Windows 11 security attributes with a modified floor set to Windows 10 build 17763 (HLK Validated and MS signed)

The test machines included:

- A Windows 10 1809 (build 17763) system installed from a pre-March 2023 ISO.

- A Windows 10 22H2 system installed via an upgrade path.

- A fresh Windows 10 22H2 installation from a recent ISO.

- A fresh Windows 11 24H2 installation.

Results:

- On a fresh Windows 10 1809 VM, the original driver targeting build 17763 installed and the device performed normally.

- On a fresh Windows 10 22H2 VM, the original driver targeting build 17763 installed and the device performed normally.

- The modified Windows 11 driver (containing Windows 11 security attributes) installed correctly on the fresh Windows 11 24H2 machine as expected.

- After installing the modified Windows 11 driver, neither the 1809 nor the 22H2 machine would subsequently install the original 17763 driver. The reader was rendered inoperable on both systems.

These results, combined with subsequent research, support the conclusions in this document.

2. The Conclusion:

Version Promotion is a One-Way Gate System hardening can occur when a driver contains directives that cause the kernel to upgrade UMDF from 2.15 to 2.25. While some research suggests this may be more pronounced with biometric drivers, the effect appears broader.

- Version Lock: Once a system promotes a device class to the 2.25 tier, OS-level trust is permanently raised.

- Inoperability: Attempting to use a 2.15 driver afterward renders it inoperable on that machine.

- The transition from UMDF 2.25 back to 2.15 is a simplification of a far more complex process involving HVCI, attestation requirements, and the removal of transitional compatibility layers.

Clarification: Why “Rollback” Is No Longer Practical Microsoft documentation suggests rollback should still be possible. In practice, however, the mechanisms required to restore prior UMDF behavior are no longer present on many systems.

3. The "Legacy" Illusion

Older drivers may continue to function on systems that have never been hardened. This creates the illusion of superior compatibility when, in reality, they have simply never encountered the new security enforcement.

4. The Role of Windows Biometric Framework

(WBF) Biometric devices operate under WBF’s internal enforcement logic, which is more restrictive than general driver loading. A device may appear healthy in Device Manager yet remain blocked from full functionality.

5. Timeline: How We Reached the Current State (2012–2026)

2012–2015: Foundation Phase Windows 8 and early Windows 10 established UMDF 2.x as the future of user-mode drivers, with broad legacy tolerance.

2018: Transitional Baseline (Windows 10 1803) Microsoft introduced core technologies (HVCI, modern code integrity, updated UMDF) but left them largely disabled by default. UMDF 2.15 became the de-facto transitional layer.

2023: Security Posture Shift Microsoft began actively promoting kernel isolation and memory integrity. Windows installation media and servicing behavior changed to limit fallback to legacy paths.

Late 2023: Broad Adoption of Hardened Defaults Security notifications drove widespread enablement of modern enforcement. Legacy drivers began failing on hardened systems.

2024–2026: Enforcement Becomes the Baseline Windows 11 24H2 and 25H2 formalized kernel isolation and modern code integrity as assumed platform conditions. Transitional compatibility is no longer dependable.

6. The Shift in Windows Security Posture

Up until March 2023, Microsoft did not enable Core Isolation (HVCI / Memory Integrity) without explicit user consent — either during the upgrade process or via an automated update.

In 2023, Microsoft designated HVCI as a “mandatory health requirement” and began pushing the feature more aggressively through security updates. This marked a change in behavior, with some systems having the flag enabled without direct user interaction.

This action met with widespread criticism. As a result, the “Health” update was pulled back. It was later replaced with a strong, persistent notification encouraging users to “update their system now” due to security concerns. This notification was notably flagged with a yellow warning icon and remained highly visible.

Microsoft has a well-established pattern of using UI prompts, persistent notifications, and recommended actions to guide users toward its preferred security configurations.

The aggressive promotion of Memory Integrity (HVCI / Core Isolation) followed this exact pattern.

You can draw your own conclusions about whether this outcome aligns with Microsoft’s long-standing encouragement to upgrade from Windows 10 to Windows 11.

That point is irrelevant. Microsoft has been telling us all along this time is coming.

7. Previous and Current Driver Identification Paradigms

Microsoft has long advised developers to detect features rather than rely solely on Operating System version. This guidance has appeared consistently since Windows 8 (2012) across multiple documentation sources, including the Compatibility Cookbook, Version Helper API, UWP API contracts, and Feature Detection Guide.

However, in practice the industry — and even Microsoft’s own driver submission system (Product Center) — continues to primarily use OS version, code name, and architecture as the main identifying criteria. For example, the TargetOSVersion decoration format documented by Microsoft still centers on build number: “Starting with Windows 10 version 1607, the build number is the authoritative discriminator for INF OS version matching, but not a reliable indicator of feature availability, servicing baseline, or platform capability.”

This creates a fundamental gap. While HVCI and associated security features have existed since Redstone 3, they were not consistently enforced on upgrade paths. Windows 11 25H2 further tightened this by removing registry-based workarounds for “unsafe” drivers.

The reality is that there is currently no standardized, widely adopted mechanism to differentiate driver packages on the same OS build based on security feature compatibility.

A new paradigm is needed that properly accounts for modern security requirements beyond simple OS version detection.

8. Assume HVCI Is the Future (Because It Is)

Windows 11 25H2 signals the end of transitional compatibility. The following realities should be accepted as the new baseline:

- Kernel isolation is becoming mandatory.

- Registry workarounds are increasingly ineffective.

- Backward compatibility is becoming more selective.

- This trend will continue to accelerate.

9. Strategic Recommendations:

New Compatibility Metrics Organizations should transition to a Security Maturity Audit that could include known or public features such as:

- HVCI / Memory Integrity status

- Secure Boot status

- Device installation history (clean install vs. in-place upgrade)

Automating the collection of these metrics is critical to distinguish between installation errors and proactive security blocks by the Windows kernel.

10. Operational Strategy:

The Three-Tiered Forecast Drivers are now susceptible to three distinct environmental states:

  • Tier 1: Windows 10 (1803–24H2) in an unhardened state.

  • Tier 2: Windows 10 22H2 in a hardened state.

  • Tier 3: Windows 11 (24H2 and newer) in a hardened state

  1. Post-Mortem / Addressing Common Objections

This report has encountered resistance, largely because much of the observed behavior is not yet formally documented by Microsoft and represents a departure from long-standing driver compatibility assumptions.

Once Core Isolation is enabled on a system, the practical ability to revert to pre-2.25 UMDF behavior is significantly reduced. Transitional compatibility files and rollback mechanisms that previously existed are no longer present on many modern Windows 10 and Windows 11 installations. For practical purposes, “rollback” or recovery in this context is factually possible.

As noted in the Addendum, while it may overstate the situation to call this a universal new paradigm across all Microsoft drivers, the practical effect for end users is very real. In the case of biometric fingerprint readers, most users employ only one reader. When that reader (or any modern WBF driver) triggers the hardening process — typically through UMDF 2.25+ components and HVCI enforcement — the older driver becomes inoperable on that specific machine.

Based on testing and analysis, the UMDF Reflector (WUDFRd.sys) appears to be updated at a system level when this process occurs. Although Microsoft documentation suggests rollback should be possible, in practice the mechanisms required to rebuild, replace, or restore the prior version of the Reflector no longer appear to exist in a workable form. If that driver meets criteria allowing rollback, the process involves complex manual steps that are far beyond the capability of most end users.

It would be difficult to accept that all drivers built against UMDF 2.15 are universally affected, as that would imply widespread failures across many device classes (for example, printers and other common peripherals). Importantly, this has not been clearly observed in the field. It is therefore possible that there is a meaningful distinction based on driver type or device class, with the impact being more pronounced in security-sensitive scenarios such as biometric or Windows Hello–integrated devices.

That said, while this technical distinction may be significant in theory, it is largely irrelevant from the user’s perspective. When installation or use of a modern driver triggers system-level hardening, the outcome for that user is effectively the same: their device becomes inoperable on that machine. Recovery or rollback is not realistically achievable for the average user. Until a driver that meets the newer security requirements is provided, both the device and associated software appear to have failed.

The operational impact is clear: OS version number alone is no longer a reliable identifier for determining which driver package will function on a given machine. A system that has had Core Isolation enabled may reject or fail with older drivers even if the build number falls within a previously supported range.

This change effectively breaks the traditional “update by OS version” model the industry has relied upon for years. The three-tier environmental model and Security Maturity Audit proposed in Sections 9 and 10 are designed to address this new reality.

12. Final Observation

Once Core Isolation is enabled, some drivers become inoperable on that machine, even when attempting to reinstall a previously working version.

Microsoft documentation maintains that broad backward compatibility exists. However, the combination of HVCI enforcement, changes to the UMDF Reflector, and the removal of transitional components has created a significant practical barrier for continued use of older drivers on hardened Windows 10 systems.

In practice, the only reliable way to restore functionality in many cases is to deploy a valid, Microsoft-signed driver that incorporates modern Windows 11 security attributes and validation requirements, while still maintaining a minimum supported OS level that includes the users' Windows 10 Build. Such a driver must be supplied by the peripheral manufacturer, who probably doesn't offer any Windows 10 driver with Windows 11 Security Attributes.

Simply forcing a user to upgrade to Windows 11 is simply not feasible for many users and places an unnecessary burden on the consumer; in the corporate world the penalties could be severe as the user is unable to perform their duties.

Blaming anyone - Microsoft, the peripheral and driver producers, the user who can't or won't upgrade - is pointless. The fact remains that any consumer who uses an unhardened 10 or 11 OS are prone to suddenly be unable to use their peripherals (at best) and (at worst) losing access to their system -- with is no “simple” solution for fixing that problem.


r/windowsdev • • Aug 17 '21

A Decade Later, .NET Developers Still Fear Being 'Silverlighted' by Microsoft

Thumbnail
visualstudiomagazine.com
4 Upvotes

r/windowsdev • • Mar 19 '26

Seeking Specialized Windows Developer for Modern Telephony App

2 Upvotes

I have a great idea for a app that I would love to develop, I am awaiting probate on a inherited property & I know that Voice modems & Landline phones are basically obsolete I wish to do this purely for myself but I would want the app to be on the windows store, I have no idea when I will get the houses probated but I'm trying to find the right developer for my project for when the time comes, I dont want to spend anymore than $7,500, Please keep comments professional


r/windowsdev • • Jun 30 '18

Why do I need a beefier laptop for Hololens app development with a Hololens headset, than I do just using the emulator?

2 Upvotes

It’s my understanding that the Hololens is a $3500 headset because it’s a high-spec gaming computer shrunk to find around your head. So if that’s accurate, why do I need a higher spec laptop when developing with it, versus doing everything with an emulator?

Seems to me the laptop would need to be beefier to support the emulator’s resource needs, and a mid-spec laptop would be fine with a headset because it can offload the resource needs to another “computer.”

Can anyone offer some insight? Xposted from /r/Hololens. Thanks!


r/windowsdev • • Nov 17 '17

Screen Mirroring for iOS, Android, and Windows Phone

Thumbnail
montemagno.com
2 Upvotes

r/windowsdev • • Feb 04 '16

I'm new to Windows Dev and its making me want to go be a lumberjack. Please help me with some of the problems I'm hitting. Microsoft won't.

2 Upvotes

Sorry if this comes off as a little rant-y. I'm new to Windows development and its making me want to shoot myself in the face. I'm trying to write some kernel drivers. Here are some of the problems I've been having:

- Shitty APIs: Cryptography: Next Generation (CNG) has to be something somebody wrote after taking bath salts, walking into traffic, getting a concussion and going home to design an API. Everything crypto related (random number generation, hashing, encryption) is somehow shoehorned into the same interface. Crypto parameters are passed as random arguments that don't make sense (e.g. AAD and tags passed as part of "paddingInfo"). All the internal state of the algorithm implementation has to be initialized individually by the caller. If somebody on my team wrote this they'd be fired on the spot. Is there any alternative to this abomination of a library other than porting over something else?

- Shitty driver abstractions. I want to write a virtual disk driver. Windows makes me implement it as a virtual storport miniport where I have to implement SCSI. Down to the endian-ness of the fields. What the fuck. Are there any alternatives?

- Visual Studio 2015. This software that I have to pay 600$ ANUALLY for is such a piece of shit. Its mind-numbing to configure and it crashes on me left and right. I can consistently reproduce a crash by entering the kernel debugger and losing connectivity to the target host (e.g. I'm debugging a fault). Has anyone ever hit and resolved this? I can't get Microsoft to help me. Which brings me to my next and biggest issue/question.

- How the fuck do I get help for issues with this software that I'm paying boatloads of money for? I tried to file a support ticket with Microsoft and they require that I pay FIVE HUNDRED DOLLARS to file ONE support ticket for something that is clearly a bug in their code. Are you kidding me??? How else do I get help with this stuff?

Please give me some advice.