Archive for the ‘Troubleshooting’ Category

Missing Drive Space

Some users are reporting a sudden loss of drive space. It seems a recently released Microsoft Defender update is generating thousands, and even millions, of files consuming many GB of storage space. The folder where these files are located is C:\ProgramData\Microsoft\Windows Defender\Scans\History\Store

You can resolve the issue by “checking for updates” under Update and Security (Windows 10) and installing the latest Microsoft Defender update.

Printing issues after KB5000808 & KB5000802

Today started, after patch Tuesday, with many machines crashing when one tried to print resulting in the standard “Your PC ran into a problem….” with a Stop Code: APC_INDEX_MISMATCH error, due to win32kfull.sys

UPDATE: Microsoft released updates today, March 16/21 to resolve the problem but you must manually download and install:

Windows 10 emergency updates released to fix printing crashes (bleepingcomputer.com)

UPDATE 2: It seems the first patch further broke some printers resulting in blank pages or missng content. Another ‘out-of-band’ update was released the 18th.

Windows message center | Microsoft Docs

UPDATE 3: Microsoft halts the rollout for the “emergency” patch for the patch for the patch Tuesday update 😦

Microsoft halts rollout of Windows 10 KB5001649 emergency update (bleepingcomputer.com)

With my clients this seemed to happen with any Office or Windows app, even notepad. However Adobe seemed to be OK and oddly if you just right click on any file and choose print, without opening it, it seemed to be OK as well. Many report updating the printer drivers solved the problem, but doing so in my cases “Windows encountered an error”. Uninstalling the printer and reinstalling with the latest drivers did resolve the problem. Also it seems not all printers are problematic. On one system which had multiple printers, the error occurred when printing to any printer, but just reinstalling the Ricoh C2504 printer eliminated the problem for all printers. Google shows Ricoh and Kyocera printers seem to be the most problematic.

Unable to Open QuickBooks Data File

Several months after every QuickBooks Pro and Enterprise annual upgrade my clients run into an issue where they cannot connect to the QuickBooks database with messages indicating, the application cannot access the database, and H2020 Error, or QuickBooks is unable to open this company file due to the file being open on another computer in single user mode.  Most recently, as per the image below:

I have found over the years the solution is to open the services management console  ( services.msc )  on the server or computer hosting the data, scroll down to locate the QuickBooks service named “QuickBooksDBxx”, where xx = a number relating to the current version.  If you have installed multiple versions over the years there will be one for each year.  You want the one with the highest number. (note in the images below the changes have already been made)

Double click on the service to open the properties for that service and click on the “Log On” tab.  The radio button “This Account” will be checked, a QBDataServixeUserxx” name will be shown, and a hidden password entered.  Change to “Local System account”, click apply and close, then right click on the service and choose start. (NOTE: if you change this setting to service account and want to change back for some reason you will likely need to re-install QuickBooks)

You now need to run the “QuickBooks Database Server Manager” app from the programs menu, in the QuickBooks folder.  Under the Scan Folders tab make sure the folder that contains your data is shown  If not browse to it and select, then click the “Start Scan” button.  It should show “successful” when done and you can choose close.  Assuming you have the same issue, running this wizard before making the change above will result in “failure”.

Sage Many Redirected Printers

If you remote into a PC to run Sage, sometimes your local printer does not connect. To resolve this you need to open the Windows printers console on the computer running Sage and look for the appropriate printer and the “redirected #”. Then in Sage under Report & Form Options, choose the items you wish to print and beside them select the printer with the redirected # that matches the printer in the Windows printers console, as in the image below.

On many systems each time you reconnect to the remote computer a new redirected connection is created such that there are so many it can be near impossible to locate the appropriate redirected printer. See image below as an example.

To clear all these excess printers you can edit the registry. (As usual, back up the registry or at least the key before deleting and if not comfortable doing so, do not proceed as registry changes can corrupt your machine) To clean up the list of printers, on the computer running Sage, locate the registry key:
HKEY_CURRENT_USER\Software\Microsoft\Window Nt\Currentversion\Printerports
Delete all printer ports showing (redirected #). Do not delete those without (redirected #)
Reboot the computer running Sage, reconnect, and select the newly redirected printer.

Outlook fails to start

Immediately after Windows updates today on 2 different systems, so far, you cannot open Outlook.  As soon as you open it closes.  Next time you open you get the Open Outlook In Safe mode popup, which also doesn’t work.  After looking at commonalities in the two systems and trouble shooting it seems the issue was the July 14th ‘Patch Tuesday’ update “Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4565483)”.  The update includes multiple features but among them is “Updates to improve security when using Microsoft Office products.” Uninstalling the update immediately resolved the issue.

If unfamiliar with doing so go to Control Panel, click on “Programs and Features”, then “View installed updates”, locate the (KB4565483) Update, right click and choose uninstall.  As always you should have a backup of your system before adding or removing updates.

I have also selected “pause updates for 7 days” in case it tries to reinstall before Microsoft has a fix.

Update: It seems this does not always work. Instead you need to roll back Office, however Microsoft has apparently realized the problem and is pushing out the fix.  To enforce, just close Outlook and re-open.  This worked on the latest machine with which I had a problem and there was a message in Outlook about the issue when it did open.  It may not be pushed out to all machines yet so waiting a couple of hours may be necessary.  See the following link from Microsoft regarding details: https://support.microsoft.com/en-us/office/active-investigation-into-outlook-crashing-on-launch-9c59ad4b-813c-432a-afdc-f14717a4528d?ui=en-us&rs=en-us&ad=us

KB4561600 or KB4560960 ‘Breaks’ Printing

On several machines after the automatic installation of Windows updates KB4561600 and KB4560960, printing to some, but nit all, printers no longer works. It seems when you try to print, the application closes immediately and printing does not take place. The simple solution is to locate the most recent drivers, delete the existing printer and re-install using the new drivers.

Hyper-V Missing VMs

Over the past 6 months I installed 4 Server 2019 Hyper-V hosts for various clients. After several months with no problems, following a reboot, all running VM’s completely disappeared from the Hyper-V management console and were not accessible from the network using management tools, file shares, remote desktop, or even pings. Oddly, shut down or saved VM’s were present.

When this first happened I was shocked. The VHDX files were all present so I could create a new VM, but that didn’t seem practical. Googling showed that this can happen if the Hyper-V Virtual Machine Management service did not start, but in my case it had. I tried restarting the service, the VM’s instantly reappeared, and were in a running state with boot up almost complete.

This issue over the coming months started happening on other 2019 servers and after every reboot, planned or due to a power outage, I had to connect to the host and restart the Hyper-V Virtual Machine Management service.

Further Googling this issue brings up suggestions of corrupt VM configuration files, granting “NT Virtual Machine\Virtual Machines” the “logon as a service right”, doing the same with group policy, and other suggestions, but where restarting the service would resolve in every case I assumed there was not a configuration issue.

In the end setting the Hyper-V Virtual Machine Management service start up type to “Automatic (delayed start)” resolved the problem on all machines, though it resulted in a slightly longer boot time for the VMs.

All of thee servers worked fine for a few months so I assume the problem was due to a Windows update but to date I have found no actual cause. Also, I can confirm this only occurs on my 2019 Hyper-V hosts. There are no issues with Server 2016 or earlier servers.

Hyper-V restart

Update: Oct 2020. I had another server with the same issue. O/S had been installed 8 months prior and no updates applied in recent months. Setting the service as delayed start did not resolve. I had to create a scheduled task to run 10 minutes after boot up. 5 minutes did not work. The scheduled task simply pointed to a batch file with the following. (the ping command just delays the process to be sure Net Stop completes before the next line).

Net Stop VMMS
ping -n 10 127.0.0.1
Net Start VMMS
Exit

Adobe Acrobat opens, then closes

I had a client where Adobe Acrobat XI Standard, on Windows 10, worked flawlessly for several years, but recently documents would open and then after a couple of seconds close with no warning.  Reinstallation and reactivating did not solve the problem nor did many Internet search results such as registry edits.

What did work was to open Adobe and very quickly, before it closed, click  “Help” on the menu bar and then select “Check for updates”.  It did find an update, download, and install.  It worked fine after that.  I suspect a compatibility issue with a recent Windows update may have caused the problem.

100’s of Windows Commands

This is a must have pdf reference file: 

An amazing, free, current, searchable, compilation of hundreds Windows commands with explanations, syntax, and examples of their use.  And, it’s free !

https://www.microsoft.com/en-us/download/details.aspx?id=56846

Windows Commands

An Authentication error has occurred

It seems recently many users are receiving an error logging into Remote Desktop Servers (Terminal Servers) from off-site. The error reads:

KB4103725

An authentication error has occurred.
The function request is not supported.
Remote computer <ServerName>
This could be due to CredSSP encryption oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660

This is a result of a March 13th update. The previous error message was shorter, but an Apr 17 update elaborated the error message to read as above.

The link explains how to resolve using group policy but the simple fix, as of May 8th, is to apply the KM4103725 monthly rollup update. This will require a reboot on most servers, but should resolve the problem once complete.

 

Tag Cloud