There seems to be an issue with recent server versions where after promoting a server to be a Domain Controller you loose access to several key functions. The main one seems to occur when trying to access “Change adapter Options” which results in a pop up “Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item”. In addition, in some cases when you try clicking on management tools such as Gpedit.msc and Control Panel, nothing happens. You can to try to access these using “run as administrator” which doesn’t always work, or create a desktop icon for the app and click the advanced options check box for run as administrator, but I see these as tedious work arounds.
The issue seems to be related to UAC (User Access Control) which can be “tweaked” with Group Policy. Since this occurred after promoting to a DC, one should use the Group Policy Management console rather than the Local Group Policy editor.
Run the GP Management console and edit the Default Domain Policy or a Computer OU of your choice. Locate the following policy, and enable:
Computer Configuration | Windows Settings | Security Settings | Local Policies | Security Options || User Account Control: Admin approval mode for the built-in administrator account
Once changed, from an elevated Command prompt run:
If not prompted to do so, you will need to log out and back in.
You should now be able to access your various admin tools that were blocked before.
-It is very common for this to hang at 10% for quite a while. I find 10 to 30 minutes but there are those that report up to 24 hours.
-Verify the Software Protection service and the Windows License Manager services are set to automatic and running. The first may stop and start on its own as needed.
-When completed it usually requires 2 reboots to complete and the first reboot can be very slow. I have seen 6 hours.
-Though it usually automatically activates with this process, sometimes you have to manually activate after completion of the reboots. Running from the GUI does not work. You need to run from an elevated Command prompt using
Should you need to troubleshoot, there is a log created in C:\Windows\Logs\DISM
Recently after a dirty shutdown one server kept displaying the familiar “Why did the computer shutdown unexpectedly” for all users, at every logon.
Usually a reboot resolves this, but did not. I have heard of this happening over the years due to specific updates, but no updates had been applied recently. Ultimately it required locating the registry key which contains the flags to initiate the popup; \HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability and deleting any subkeys referencing the last event, such as “DirtyShutdown”. These keys get recreated after the next event. Changing values from 1 to 0 will stop the popup, but this disables it all together. Not a good idea. Of course; make sure you backup the registry before doing so and do not make changes to the registry if you are not familiar with doing so.
Recently when trying to do a Win7 to Win10 upgrade I ran into a new issue where the upgrade failed with a message; “Windows 10 couldn’t be installed” which included the detail; “We couldn’t update the system reserved partition”. Research indicates there was insufficient room despite it only requiring about 13 KB of free partition space.
Apparently this must be somewhat common as Microsoft has published a rather lengthy workaround where you delete a folder of fonts in the reserved partition but there are many steps dealing with permissions.
I tried resizing the partition with Disk Manager unsuccessfully, though I may have been able to do so with a command line and DiskPart, but before doing so, I stumbled on the following link which uses a free little partitioning tool EaseUS Partition Master. This allowed me to reduce the C partition size slightly and increase the system Reserved partition. Very slick, very easy, and worked like a charm. Windows 10 then installed trouble free.
I had to do a clean install of Windows 7 on an old PC for reasons I will not go into. After installing Win7 SP1 and a couple of drivers I ran Windows update but it failed almost immediately with Error / Code 80072EFE “Windows Update encountered an unknown error.”
I tried the familiar Windows update repairs with no success. After some research I downloaded Windows patch # KB3138612, ran it, reboot, and Windows update now worked as it should.
Suddenly many users alerting that the message body of their e-mails, using Outlook desktop app, are blank. Also they cannot type in the body of a new e-mail or reply. Microsoft has released the following statements:
Latest message, May 11, 2021 7:24 PMView historyTitle: Issue affecting viewing email content in Outlook User Impact: Users may be unable to view email message content within Outlook. More info: Impact is specific to the Outlook client and users with access to other protocols, such as Outlook on the web or the Outlook mobile app, can view message content in those platforms as a potential workaround while our fix is applied. Current status: We’ve identified the underlying cause of impact and are applying a fix. This fix will reach all affected users incrementally over the course of the next four-to-five hours. Once users receive the fix, they will need to restart their email client to apply the fix. In some circumstances, users may need to restart their client a second time for the changes to take effect. We expect to complete this process and restore service for all affected users by May 12, 2021, at 3:00 AM UTC. We encourage affected users who are able to do so to leverage the workarounds described above in the “more info” section of this post while we complete the process of fixing this problem. Scope of impact: This issue could affect any user attempting to view an email message in the Outlook client. Root cause: A recent change to systems that facilitate text display management for content within the Outlook client caused impact. Next update by: Wednesday, May 12, 2021, 12:00 AM (3:00 AM UTC)
“May 11, 2021 6:19 PMView historyTitle: Issue affecting viewing email content in Outlook User Impact: Users may be unable to view email message content within Outlook. More info: Initial reports indicate that impact is specific to the Outlook client and users with access to other protocols, such as Outlook on the web or the Outlook mobile app, can view message content in those platforms as a potential workaround. Current status: We’re continuing to analyze recent updates to the environment and the associated code as we work to isolate the cause of impact. Our efforts are focused on determining the most expedient means of remediating this issue. Scope of impact: This issue could affect any user attempting to view an email message in the Outlook client. Next update by: Tuesday, May 11, 2021, 7:30 PM (10:30 PM UTC)“
“May 11, 2021 5:28 PMView historyTitle: Issue affecting viewing email content in Outlook User Impact: Users may be unable to view email message content within Outlook. More info: Initial reports indicate that Outlook on the web is unaffected and users with access to Outlook on the web can view email messages there while we work on a solution. Current status: We’re gathering and analyzing data in an effort to isolate the cause of impact. Initial reports indicate that impact is specific to the Outlook client and users with access to other protocols, such as Outlook on the web or the Outlook mobile app, can view message content in those platforms as a potential workaround. Scope of impact: This issue could affect any user attempting to view an email message in the Outlook client. Next update by: Tuesday, May 11, 2021, 6:30 PM (9:30 PM UTC)”
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.
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:
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.
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”.
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.