Ask any Windows administrator what is on the screen of the server they are remoted into, and the good ones can tell you at a glance: the machine name, the IP, the OS build, who is logged in. For two decades the reason they can do that is a single Sysinternals utility called BGInfo, which stamps that information straight onto the desktop wallpaper. It is one of those tools that quietly runs on millions of machines and almost never gets talked about. BgLight is a deliberate, modern rebuild of that idea, and it comes from navanem.
BgLight is an open source, one-shot Windows tool that paints a styled system-information panel onto the desktop background and then gets out of the way. No installer, no tray icon, no resident service. It is built by navanem.com, the same Geneva based security and IT lab that ships its tools only after running them in a real environment.
The lab behind the tool
navanem.com calls itself swiss made for sysadmins, and the work backs the slogan up. It is a solo built lab run by Emanuel De Almeida, an IT engineer based in Geneva, publishing security news, curated CVE advisories, deep dive tutorials, troubleshooting fixes, plain English explainers, PowerShell scripts, browser based tools, and a small set of open source projects.
The pattern across all of it is the same: pick a problem an administrator actually hits, solve it without bloat, and hand the result over for free. BgLight fits that mould exactly. It does one job, it does it on a schedule, and it leaves nothing running behind it.
Why BGInfo still matters, and where it shows its age
The case for desktop info panels has not changed. When you are jumping between dozens of RDP sessions, having the hostname, domain, IP and serial number printed on the wallpaper removes a whole class of small mistakes, the kind that end with a command run against the wrong box. For asset tracking and incident response, a serial number you can read without opening a single dialog is genuinely useful.
What has aged is the tooling around the idea. The classic approach leans on a configuration file, a GUI to edit it, and a setup that predates modern deployment habits. BgLight keeps the outcome and drops the ceremony. There is no UI to configure, because every option is a command-line flag, and the whole thing is a single executable you can drop onto a share and call from a logon script.
What BgLight actually does
Run BgLight.exe once and it collects the machine state, renders a translucent panel with rounded, anti-aliased corners, writes it to a bitmap, and applies that bitmap as the wallpaper. Then it exits. The panel shows nine fields in two aligned columns: the logged in user as domain\username, the processor, the BIOS serial number, active IPv4 addresses, the OS edition and build, RAM used against total, free and total disk on C:, the Active Directory domain or workgroup, and the timestamp of the last refresh. Sizes are reported in real gibibytes, base 1024, not the rounded marketing numbers.
A bold header carries the computer name with an accent line above it, and a footer carries the version and attribution. If a single query fails, that field shows N/A and the rest of the panel renders normally, so one flaky WMI call never takes the whole thing down.
Appearance is yours to set. Position drops the panel into any of the four corners, and accent colour, background colour, font name, font size and output path are all flags:
BgLight.exe /position=TopRight /accentColor=#0078D4 /fontSize=11 /fontName="Segoe UI"
Built for deployment, not for clicking
This is where BgLight earns its keep in a fleet. Because it is one self-contained executable with no install step, you deploy it the way you already deploy scripts. Point a scheduled task at it to refresh every thirty minutes or so, or wire it into a GPO logon script using the deploy\run-bglight.bat helper that ships with the project. Errors are written to a log.txt in the output directory, so a silent tool still leaves a trail when something goes wrong.
The only runtime requirement is .NET Framework 4.8, which is already present on every supported Windows 10 and 11 install, so there is nothing to stage ahead of it. The usual caveats apply and the project is honest about them: a GPO that forces a specific wallpaper will override BgLight, and an output path the account cannot write to will need either a writable location or elevated rights.
Under the hood
BgLight is written in C# on .NET Framework 4.8, and the design is a clean four-stage pipeline. AppConfig.Parse reads the arguments and fills in defaults, SystemInfoCollector.Collect gathers the data with each source wrapped in its own try/catch, WallpaperRenderer.Render draws the panel with GDI+ and saves the bitmap, and WallpaperSetter.Apply calls the Win32 SystemParametersInfo function to set it. It pulls hardware and OS facts from WMI and the standard .NET APIs, with no third party packages in the chain.
You can build it yourself with dotnet build BgLight.sln -c Release, no Visual Studio required, and there is a test project you run with dotnet test. The current release at the time of writing is v1.2.1.
The bigger point
BgLight is a small tool, and that is the point. It takes a job administrators have relied on for twenty years, rebuilds it as a single dependency-free executable that fits modern deployment, and gives it away under an open licence. No agent, no UI, no data leaving the machine. If you run Windows at any scale, it is a few minutes of setup for a panel that quietly pays for itself the first time it stops you acting on the wrong server.
You can read the full write-up on the official project page, or go straight to the source on GitHub.
