<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>WindowsServices on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/windowsservices/</link><description>Recent content in WindowsServices on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 12 Mar 2026 08:22:30 +0100</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/windowsservices/index.xml" rel="self" type="application/rss+xml"/><item><title>Fail Closed: Best Practices for Service Startup Behavior and Logging</title><link>http://blog.marko-apfel.de/posts/service-startup-and-logging/</link><pubDate>Thu, 12 Mar 2026 08:22:30 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/service-startup-and-logging/</guid><description>A service that limps along in a broken state is worse than one that stops. Here&amp;rsquo;s a fail-closed approach to startup failures, and a logging structure that keeps operators in the loop.</description></item></channel></rss>