Update 2017-05-02: I’ll attempt to keep this up to date as new versions of Windows come out. This might seem like an odd topic to cover, but I’ve receive quite a few questions about this in recent months. Due to Windows 10 being developed constantly and on a rapid release schedule, it’s important to differentiate between the various major updates. Even though Windows 10 Anniversary Update (1607) seems very similar to what would have been called Windows 10 RTM in the past, there are some big changes, and keeping track of each major update can be tricky when traditionally IT Pro’s are used to a new version of Windows every few years rather than every few months.
If you’ve installed a fresh install of Windows 10 1607/Windows Server 2016 recently, you may have experienced a problem when it tries to download and install updates from your local WSUS server - specifically, it doesn’t, it gets stuck. You’ve tired rebooting, stopping the BITS and WU services, deleting %systemroot%\SoftwareDistribution but nothing seems to work. Both Windows 10 1607 and Windows Server 2016 require a cumulative update that fixes this specific issue.
Update 2018-04-20: I’ve rolled the information in this post, and updated it, into a new post about setting up a WSUS server from scratch on Windows Server 2016 Core. The post is also suitable for a regular Windows Server 2016 server with a GUI. You can read it here. Update: I’ve tested and updated this post for Windows Server 2016. In this post, I’m going to walk through setting up a WSUS server from scratch on Windows Server 2012 R2 or Windows Server 2016.
Update 2018-04-20: I’ve rolled the information in this post, and updated it, into a new post about setting up a WSUS server from scratch on Windows Server 2016 Core. The post is also suitable for a regular Windows Server 2016 server with a GUI. You can read it here. Update 2017-05-03: If you’re looking to resolve similar problems with WSUS on Windows Server 2016, please see this post. If you’ve been managing a WSUS server, you may have run into the well known MMC connection error above (appears as Event ID 7053 in the Event Viewer) by now.
If you’ve seen the news from the latest Microsoft Event, you’ll know that the next Windows 10 update, dubbed the “Creator Update” will be out early next year. One of the new tools shown was Paint 3D which looks to make the creation of 3D content more accessible. You can check it out right now, if you are a member of the Windows Insider Preview Program - which anyone can join.
Today’s post is another PowerShell script I wrote with a very specific task in mind. Chatty is a popular chat application for streaming site Twitch.tv. It is generally used for interacting in channel chat rooms as well as logging, running scripts, and live statistics. Some users run it 24/7. One problem that exists is that the logs don’t get separated, even if the program is restarted, the log continues on in the same file.
One of the servers I manage is a Minecraft server for a friend. It’s called Marzicraft, it has a candy theme, and it’s delightful, even if I do say so myself. :) I recently replaced the .bat scripts I wrote to maintain it with a single PowerShell script. Even if you aren’t supporting a Minecraft server, hopefully there’s some useful information here for your own work. If you are intending to use this script for your own Minecraft server, please be aware that I’ve put this together with a dedicated server in mind.