Sometimes . . . Grrrr


There are occasions when Microsoft Windows will make life so difficult that murder becomes an attractive option. I can usually have a go at fixing a problem when I know what the problem is. But then there are times when even knowing the problem leaves you in the dark when trying to fix them.

Windows 10

Today was one such occasion. It started yesterday evening when my laptop informed me that Windows needs to restart to complete the latest update. I like to get things like that out of the way as soon as possible, so I did the required restart and cracked on with some other stuff I needed to do.

It became apparent after about 40 minutes that something was amiss. The screen showed the usual blue update screen warning me not to turn my computer off as it was ‘working’ on the updates and was at 0%. Twenty minutes later, it was still at 0%!

It was then that I took drastic action and put my laptop into ‘sleep mode’. Upon waking up again everything seemed fine until it got stuck again 10 minutes later. A bit more sleep mode and then the update finished. By this time it was getting late and I decided that I needed to go into ‘sleep mode.’

<><><>

SFC.exe

This morning new problems appeared. Everything was running very slowly and some applications were simply refusing to open. I remembered from my previous job that if there was a problem, I should run the “System File Checker” (sfc.exe). This would find the problem and I could then look for a solution. It took about 2½ hours to run, but the system still seemed slow. I was contemplating how I could explain that I needed a new machine when a pop-up occurred telling me that ‘Windows needs to restart …” again. A quick look in the update settings told me that the previous update had not been installed.

Once again I restarted my laptop and after a good 30 minutes, I was back up and running. This time everything was back to normal speed and all the applications were behaving themselves. I’m thinking that yesterdays update file was corrupted somehow and a new version of the update fixed everything. But who knows?