Articles related to WSUS server
A few months ago, during my WSUS adventures with the database and IIS pool problems, I spotted an additional issue. The WSUS database with its transaction log is installed on drive C.
C drive is a system drive and it shouldn’t be used for any storage of data. Even more, you can achieve up to 30% better operations with the MS SQL server when the database and its log are on separate physical drives or virtual disks. Continue reading
In my recent posts, I described the problems with the inaccessible WSUS server. The first problem was related to the stopped WSUS database and I quickly solved it.
The second problem was more complex and I spent an hour narrowing it down to the stopped WSUS application pool in IIS. I found a temporary solution – to manually start the application pool every time the service crashes.
In the past few weeks, I had a series of problems with the WSUS server. It just stops. So, I need to check the server and fix the problem.
In most cases, I spotted the problem when I tried to update my laptop. While trying to check for new updates, I am getting one of the many update related errors. In this case, the error 80072EE2.
A few days ago I updated my office laptop to Windows 10 build 1703. This part passed fine. However, after the reboot, Windows update reported an error with code 80244022. The explanation of this error is unclear – something went wrong.
After a few restarts, many retries, even deletion of the Software Distribution folder from the Windows folder, I searched the Net. Many answers were like “it’s just gone”. As my error isn’t just gone with the wind, I knew that it’s time for the HEV suite, crowbar and deep dive into the world of logs and Windows services.
MiViLiSNet 