{"id":13165,"date":"2025-10-27T06:54:40","date_gmt":"2025-10-27T13:54:40","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=13165"},"modified":"2025-10-27T06:54:40","modified_gmt":"2025-10-27T13:54:40","slug":"version-11-released","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/service-protector\/version-11-released\/","title":{"rendered":"Service Protector 11: Resource Monitoring, Help for Slow Services, and More"},"content":{"rendered":"<div align=\"center\"><img loading=\"lazy\" decoding=\"async\" class=\"no-lazy-load\" style=\"margin-bottom:20px;\" src=\"\/blog\/images\/new-release-400x250.webp\" title=\"Service Protector 11: Resource Monitoring, Help for Slow Services, and More\" alt=\"Service Protector 11: Resource Monitoring, Help for Slow Services, and More\" border=\"0\" width=\"400\" height=\"250\"><\/div>\n<p>Our team released <a href=\"\/products\/ServiceProtector\/\">Service Protector<\/a> 11.0 on October 25. Here&#8217;s what&#8217;s included in this new and improved version:<\/p>\n<h2 class=\"blog-caption\">Automatically restart your Windows Service if it consumes too many resource handles<\/h2>\n<p>Is your Windows Service a &#8220;resource hog&#8221;? Does it chug away in the background, quietly accumulating references to files, registry keys, tokens and other operating system objects?<\/p>\n<p>If left unchecked, bad things can happen in that situation. For example, your service can eventually tie up so many handles that it crashes. Or worse, it can hang, turning into a stumbling zombie that refuses to do its job.<\/p>\n<p>Service Protector 11 is here to help you mitigate those tricky scenarios. It features a new sanity check that monitors resource handles and takes action when the count spikes above a given threshold.<\/p>\n<h3>How to monitor operating system handles with Service Protector<\/h3>\n<p>The &#8220;check resource handles&#8221; sanity check is very easy to use. For example, we already have the <a href=\"\/blog\/windows-services\/spooler\/\">Print Spooler Windows Service<\/a> protected on our server. To ensure that the service is quickly restarted if it consumes more than 500 handles, we would:<\/p>\n<ol>\n<li>\n<p>Edit the Spooler service in Service Protector.<\/p>\n<\/li>\n<li>\n<p>Switch to the <b>Monitor<\/b> tab.<\/p>\n<\/li>\n<li>\n<p>Check the <b>Whenever it fails a periodic sanity check<\/b> box and click the <b>Set<\/b> button to the right:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/service-protector-set-new-sanity-check.png\" class=\"zoomPopup\" title=\"Activate a new sanity check to monitor your Windows Service\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/service-protector-set-new-sanity-check.png\" title=\"Activate a new sanity check to monitor your Windows Service (click to enlarge)\" alt=\"Activate a new sanity check to monitor your Windows Service\" border=\"0\" \/><\/a><\/div>\n<\/li>\n<li>\n<p>In the &#8220;Add Sanity Check&#8221; window that pops up, choose <b>Check that your service doesn&#8217;t have too many resource handles open<\/b> from the list and click <b>Next<\/b> to proceed:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/service-protector-choose-resource-handles-sanity-check.png\" class=\"zoomPopup\" title=\"Choose the resource handles sanity check\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/service-protector-choose-resource-handles-sanity-check.png\" title=\"Choose the resource handles sanity check (click to enlarge)\" alt=\"Choose the resource handles sanity check\" border=\"0\" \/><\/a><\/div>\n<\/li>\n<li>\n<p>Enter 500 in the <b>Maximum handle count<\/b> field:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/service-protector-enter-maximum-handle-count.png\" class=\"zoomPopup\" title=\"Enter the maximum resource handle count\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/service-protector-enter-maximum-handle-count.png\" title=\"Enter the maximum resource handle count (click to enlarge)\" alt=\"Enter the maximum resource handle count\" border=\"0\" \/><\/a><\/div>\n<\/li>\n<li>\n<p>After clicking the <b>Next<\/b> button, specify how often Service Protector should check the service. Every 5 minutes is a good starting point; we can always change it later:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/service-protector-check-handle-count-regularly.png\" class=\"zoomPopup\" title=\"Check the service regularly\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/service-protector-check-handle-count-regularly.png\" title=\"Check the service regularly (click to enlarge)\" alt=\"Check the service regularly\" border=\"0\" \/><\/a><\/div>\n<\/li>\n<li>\n<p>Moving on, confirm that the sanity check is configured as expected and click <b>Add<\/b> to confirm:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/service-protector-confirm-check-resource-handles.png\" class=\"zoomPopup\" title=\"Confirm the resource handle sanity check\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/service-protector-confirm-check-resource-handles.png\" title=\"Confirm the resource handle sanity check (click to enlarge)\" alt=\"Confirm the resource handle sanity check\" border=\"0\" \/><\/a><\/div>\n<\/li>\n<li>\n<p>Save all changes in Service Protector.<\/p>\n<\/li>\n<\/ol>\n<p>And that&#8217;s it. With the sanity check keeping watch, Service Protector will automatically recycle the Spooler service if it sucks up too many resources.<\/p>\n<hr class=\"blog-section\">\n<div style=\"width:100%;margin-bottom:30px;\">\n<div style=\"margin:0px;float:right;\"><a href=\"#top\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/cdn.coretechnologies.com\/images\/top.jpg\" border=\"0\" width=\"50\" height=\"18\" title=\"Go to the top\" alt=\"\" \/><\/a><\/div>\n<\/div>\n<h2 class=\"blog-caption\">Increase the time for Windows Services to start<\/h2>\n<p>Let&#8217;s face it &mdash; some Windows Services take ages to start. And when they dilly-dally too long, the <a href=\"https:\/\/en.wikipedia.org\/wiki\/Service_Control_Manager\" target=\"_blank\">Service Control Manager<\/a> may tire of waiting and shut them down.<\/p>\n<p>If this is happening on your machine, you may see events 700 and 7009 in the Event Log. That&#8217;s the telltale sign of a slow moving service.<\/p>\n<p>But there&#8217;s a workaround. As described in <a href=\"\/WindowsServices\/FAQ.html#TimeoutOnStart\">this entry in the Windows Services FAQ<\/a>, you can update a registry value to give your services more than 30 seconds to come up to speed. Today, we&#8217;re pleased to announce that Service Protector 11 makes it super easy to update that registry setting. Simply select <b>Tools &gt; Set Service Start Timeout<\/b> and enter a duration that works better for your services:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/set-start-service-timeout.png\" class=\"zoomPopup\" title=\"Set the start timeout for all Windows Services\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/set-start-service-timeout.png\" title=\"Set the start timeout for all Windows Services (click to enlarge)\" alt=\"Set the start timeout for all Windows Services\" border=\"0\" \/><\/a><\/div>\n<p>The setting applies to all services so please keep that in mind.<\/p>\n<hr class=\"blog-section\">\n<div style=\"width:100%;margin-bottom:30px;\">\n<div style=\"margin:0px;float:right;\"><a href=\"#top\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/cdn.coretechnologies.com\/images\/top.jpg\" border=\"0\" width=\"50\" height=\"18\" title=\"Go to the top\" alt=\"\" \/><\/a><\/div>\n<\/div>\n<h2 class=\"blog-caption\">Register Service Protector online<\/h2>\n<p>Over the next few months, we&#8217;ll be rolling out a simple and straightforward online registration system. Instead of handling the serial number and registration code as you do in the offline process, you&#8217;ll have the option of doing everything from the computer where the software&#8217;s installed. Early feedback is that it&#8217;s a time-saving improvement!<\/p>\n<p>Choose <b>Register Online<\/b> from the <b>Help<\/b> menu to get started. It&#8217;s self-explanatory from there on out:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/register-service-protector-11-online.png\" class=\"zoomPopup\" title=\"Register Service Protector 11 online\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/register-service-protector-11-online.png\" title=\"Register Service Protector 11 online (click to enlarge)\" alt=\"Register Service Protector 11 online\" border=\"0\" \/><\/a><\/div>\n<hr class=\"blog-section\">\n<div style=\"width:100%;margin-bottom:30px;\">\n<div style=\"margin:0px;float:right;\"><a href=\"#top\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/cdn.coretechnologies.com\/images\/top.jpg\" border=\"0\" width=\"50\" height=\"18\" title=\"Go to the top\" alt=\"\" \/><\/a><\/div>\n<\/div>\n<h2 class=\"blog-caption\">Other fixes &amp; improvements<\/b><\/h2>\n<ul>\n<li>\n<p>The developers fixed a coding bug that truncated the descriptions of the Windows Services created by Service Protector. Fortunately the problem was purely cosmetic &mdash; operation was not affected in any way.<\/p>\n<\/li>\n<li>\n<p>Service Protector now provides better guidance (and helpful links) when someone installs a new version that doesn&#8217;t comply with the <a href=\"\/products\/ServiceProtector\/FAQ.html#Upgrade\">upgrade policy<\/a>. Here&#8217;s what that feedback looks like:<\/p>\n<div align=\"center\"><a href=\"\/blog\/images\/service-protector-upgrade-policy-enforced.png\" class=\"zoomPopup\" title=\"Service Protector's upgrade policy enforced\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"image-padding\" src=\"\/blog\/images\/service-protector-upgrade-policy-enforced.png\" title=\"Service Protector's upgrade policy enforced (click to enlarge)\" alt=\"Service Protector's upgrade policy enforced\" border=\"0\" \/><\/a><\/div>\n<\/li>\n<\/ul>\n<p style=\"padding-top:10px\">\nAs usual, please review the <a href=\"\/products\/ServiceProtector\/VersionHistory.html\">release notes<\/a> for the full list of features, fixes and improvements included in Service Protector version 11.0.<\/p>\n<hr class=\"blog-section\">\n<div style=\"width:100%;margin-bottom:30px;\">\n<div style=\"margin:0px;float:right;\"><a href=\"#top\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/cdn.coretechnologies.com\/images\/top.jpg\" border=\"0\" width=\"50\" height=\"18\" title=\"Go to the top\" alt=\"\" \/><\/a><\/div>\n<\/div>\n<h2 class=\"blog-caption\">Upgrading to Service Protector 11<\/h2>\n<p>If you purchased Service Protector <b>version 10 (after May 2024), you can upgrade to version 11 for free<\/b>. Simply download and install over your existing installation to preserve all services and settings. That way, your registration will continue to work.<\/p>\n<p>If you bought Service Protector <b>9 or earlier (before May 2024), you will need to upgrade to use version 11<\/b>.<\/p>\n<p>Please <a href=\"\/products\/ServiceProtector\/buy\/\">buy upgrades here &mdash; at a 50% discount<\/a>.<\/p>\n<p>See the complete <a href=\"\/products\/ServiceProtector\/FAQ.html#Upgrade\">upgrade policy<\/a> for more details.<\/p>\n<p style=\"padding-top:10px\">Enjoy!<\/a><\/p>\n<div align=\"center\">\n<div class=\"cta-button-1\">\n<table role=\"presentation\" cellspacing=\"0\" cellpadding=\"0\" border=\"0\" align=\"left\">\n<tbody>\n<tr>\n<td align=\"center\"><a href=\"\/blog\/tag\/service-protector-tag\/\" title=\"More articles about Service Protector\"><span><nobr>Read more about Service Protector&#8230;<\/nobr><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n<!-- relpost-thumb-wrapper --><div class=\"relpost-thumb-wrapper\"><!-- filter-class --><div class=\"relpost-thumb-container\"><style>.relpost-block-single-image, .relpost-post-image { margin-bottom: 10px; }<\/style><h3>You may also like...<\/h3><div style=\"clear: both\"><\/div><div style=\"clear: both\"><\/div><!-- relpost-block-container --><div class=\"relpost-block-container relpost-block-column-layout\" style=\"--relposth-columns: 3;--relposth-columns_t: 2; --relposth-columns_m: 2\"><a href=\"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/alwaysup-version-8-0-released\/\"class=\"relpost-block-single\" ><div class=\"relpost-custom-block-single\"><img decoding=\"async\" loading=\"lazy\" class=\"relpost-block-single-image\" alt=\"New Version\"  src=\"https:\/\/www.coretechnologies.com\/blog\/wp-content\/uploads\/new-version-150x150.png\" style=\"aspect-ratio:1\/1\" style=\"aspect-ratio:1\/1\"><\/img><div class=\"relpost-block-single-text\"  style=\"height: 75px;font-family: Arial;  font-size: 12px;  color: #333333;\"><h2 class=\"relpost_card_title\">AlwaysUp Version 8.0 Released<\/h2><\/div><\/div><\/a><a href=\"https:\/\/www.coretechnologies.com\/blog\/windows\/windows-8-1-end-of-life\/\"class=\"relpost-block-single\" ><div class=\"relpost-custom-block-single\"><img decoding=\"async\" loading=\"lazy\" class=\"relpost-block-single-image\" alt=\"Windows 8.1 End of Life: January 10, 2023\"  src=\"https:\/\/www.coretechnologies.com\/blog\/wp-content\/uploads\/windows-8.1-150x150-1.webp\" style=\"aspect-ratio:1\/1\" style=\"aspect-ratio:1\/1\"><\/img><div class=\"relpost-block-single-text\"  style=\"height: 75px;font-family: Arial;  font-size: 12px;  color: #333333;\"><h2 class=\"relpost_card_title\">Windows 8.1 End of Life: January 10, 2023<\/h2><\/div><\/div><\/a><a href=\"https:\/\/www.coretechnologies.com\/blog\/service-protector\/restart-stuck-service-feature\/\"class=\"relpost-block-single\" ><div class=\"relpost-custom-block-single\"><img decoding=\"async\" loading=\"lazy\" class=\"relpost-block-single-image\" alt=\"Service Protector Feature Spotlight: Restart A Stuck Service\"  src=\"https:\/\/www.coretechnologies.com\/blog\/wp-content\/uploads\/stuck-windows-service-150x150-1.webp\" style=\"aspect-ratio:1\/1\" style=\"aspect-ratio:1\/1\"><\/img><div class=\"relpost-block-single-text\"  style=\"height: 75px;font-family: Arial;  font-size: 12px;  color: #333333;\"><h2 class=\"relpost_card_title\">Service Protector Feature Spotlight: Restart A Stuck Service<\/h2><\/div><\/div><\/a><\/div><!-- close relpost-block-container --><div style=\"clear: both\"><\/div><\/div><!-- close filter class --><\/div><!-- close relpost-thumb-wrapper -->","protected":false},"excerpt":{"rendered":"<p>Our team released Service Protector 11.0 on October 25. Here&#8217;s what&#8217;s included in this new and improved version: Automatically restart your Windows Service if it consumes too many resource handles Is your Windows Service a &#8220;resource hog&#8221;? Does it chug &hellip; <a href=\"https:\/\/www.coretechnologies.com\/blog\/service-protector\/version-11-released\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":13166,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[382,109,393,123,138,147,392],"class_list":["post-13165","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-service-protector","tag-check-handle-count-sanity-check","tag-new-release","tag-online-registration","tag-product-registration","tag-sanity-check","tag-service-protector-tag","tag-start-service-timeout"],"_links":{"self":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/posts\/13165","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/comments?post=13165"}],"version-history":[{"count":13,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/posts\/13165\/revisions"}],"predecessor-version":[{"id":13181,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/posts\/13165\/revisions\/13181"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/media\/13166"}],"wp:attachment":[{"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/media?parent=13165"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/categories?post=13165"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.coretechnologies.com\/blog\/wp-json\/wp\/v2\/tags?post=13165"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}