I have a laser printer at home. It’s an HP LaserJet Professional CP1025NW. It’s a dandy colour printer. When I want to use it with my Windows 10 computers I go to the HP support webpage and download the appropriate driver and go from there. For some reason Windows wants to install the HP LaserJet Professional CP1020 series driver which must have something related to the CP1025NW driver. It never properly installed on my Windows 8.1 computers and it’s now doing the same thing with the Windows 10 computers I have. Every time new updates are released Windows 10 tries with all its might to install that CP1020 driver and every time it results in this:
What I would like to do is uncheck the requirement/option that insists on updating this particular driver. Sadly, this isn’t available to me. I can understand why that is. Microsoft is doing its best to protect people who run with scissors. Budding trapeze artists who use no safety net. I had a chat the other day with one of the smart people I work with about my printer driver dilemma and he pointed me to this support article KB3073930. There are a couple of excellent suggestions in the article but there’s also an actual work around to “make it stop” trying to install the driver.
When you download and run the wushowhide.diagcab file available on the support article page it does a quick scan of your machine and presents you with the option to Show or hide updates.
I selected Hide updates and was presented with a list of drivers including the “offending” driver.
I selected the driver and click next and the wizard begins “Resolving problems”. The wizard completes and resolves the problem. If the situation changes with that driver I can always rerun the wizard and Show hidden updates to allow Windows to update it successfully.
Four days ago I noticed a serious drop in performance on my five year old Dell Studio laptop. An uncomfortable change in behavior was happening that appeared to be coming out of the blue. The system would degrade to the point where it was almost unusable. CPU stats would climb to 42% in Task Manager and stick there. The fan would jump to full power and stay there.
I went over what I might have changed or installed: a new password database application, and update to WinZip, some Microsoft updates, beta Firefox. Nothing really that should have caused the drag in performance that I was seeing. Symantec? I downloaded and installed MalwareBytes to scan for malware or anything malicious that might be present. Its been a really long time, years, since I’ve had any sort of virus issue so I wasn’t really surprised when the scans came back negative.
Next I looked at the hardware. Had something failed? I ran the diagnostics on the hardware and everything responded as ok. Wow, weird. So next I decided to remove the newer software, starting with the Firefox, and see if perhaps one of the new programs was causing the discomfort. No such luck. Uninstalled it and a couple of older programs I no longer use, did a clean up of the disk, installed CPUID’s HW Monitor to get an idea of how the hardware was behaving. The exhaust port was hot to the touch. The cpu seemed to be throwing off a lot of heat. HW Monitor told me the cpu was super hot, the cores were all pinned at 100%. Without running anything the cpu was being taxed like crazy.
Digging around online I found a few articles pointing to the weird 42% cpu thing but nothing that seemed related to my situation. Last night I found something different. There are a couple, more than a couple, of references to changes in how virtual memory is managed by Windows 10. This is something I haven’t changed in ages, Windows has been doing a good job of managing this. I don’t know what changed it but it definitely changed. So, I right click Start, select System, select Advanced system settings, select Settings under Performance on the Advanced tab. Select the Advanced tab on Performance Options and click Change on the Virtual Memory option. I uncheck the Automatically manage paging file size for all drives option and set the Custom size to the Recommended option at the bottom. Close everything up, reboot the laptop, and everything is back to normal.
I can only imagine that when the last set of updates were applied it maybe reset something? I’m going to watch it for a few days then try and switch it back and see what it does. Weird.
I’m dropping this here for future reference. It’s a lovely catchall of the many Microsoft tools for Windows deployment.
Oh ya, did I mention I passed 70-347? Well I did! Another MCSA to add to my transcript. Now, back to work on 70-417.
I have successfully updated three of the Windows 10 machines here at home but the fourth, the one I use regularly and often, just won’t go. From what I see online the problem is related to the installation of the Windows DVD player KB3081704 which appears to be successfully installed on this computer. Interestingly I see the updates download and run and appear to go to 100% before they crap out. I haven’t seen the November update yet on this machine. I’m not a big fan of the way Microsoft is presenting the details of the updates. The “learn more” and “details” links provide fairly useless information. I’m hoping this changes. If Microsoft is going to provide more frequent updates in the background to keep Windows 10 current it would be super useful if they also provide lots of details of what’s being updated and why.
I passed a Microsoft exam today for 70-346: Managing Office 365 Identities and Requirements which is the first half of the requirements for the MCSA: Office 365 certification. We’ve done a few Office 365 migrations at work and from the sounds of it things are going to be busy in the Fall.
I was tasked with doing some upgrades for a client in their Configuration Manager 2012 environment recently. They wanted the SQL database on the back end upgraded to something more recent so SQL Server 2012 it is. So we confirmed we met all of the software prerequisites and began the upgrade. Setup Support Rules were happy.
Look at all those green check marks!
All of the features were auto-populated showing that they were already installed and supported. We confirmed we had adequate disk space, more little green check marks.
Many more little green check marks.
The Upgrade Rules were checked and many more little green check marks were displayed and now we’re ready to upgrade.
Ready, Set, Go!
The process begins, everything looks happy, the upgrade appears to be proceeding as planned and then this happened.
Ouch, so much red it makes my eyes hurt.
So we reviewed the logs, double-checked the prerequisites yet again, searched and researched to see if we could find out what was missing. No luck looking at entries in the log files so I did a quick search using “an error occurred for a dependency of the feature” and came across this which pointed to an already installed SQL Server 2012 component, the Microsoft SQL Server 2012 Native Client. It may have been installed as part of the SQL Server 2012 Upgrade Advisor which seems odd but I was a bit surprised that the rule checks didn’t flag the item when all the little green checks came up. All’s well that ends well. We removed the native client, reran the installation process and SQL Server 2008 R2 was successfully upgraded to SQL Server 2012.