The Acumen IT Support blog provides you with helpful articles about Microsoft Windows.

Several web sites provide good overviews.

Official Microsoft Support page

Microsoft Wikipedia


SOLVED: File Explorer Unresponsive with Windows 10


Are you having trouble with File Explorer? Do you have the Windows 10 upgraded feature pack?

At Acumen, one of our technicians was experiencing a problem with the new feature, too, so he found a solution.

But first, let’s describe the problem:


After upgrading Windows 10 to a new feature pack, the quick access section displays the message “Working on it,” then the section becomes unresponsive entirely.

Quick Access in File Explorer

File Explorer Solution:

  1. Restore Explorer
    1. To do this, open task manager, then select Windows Explorer and click “Restart.”
  2. To fix, “Start > Run > Explorer c:/Windows”
  3. Open File Explorer > Right click “Quick Access” on the Navigation Panel > “Options” > “Clear & Restore Defaults”
  4. As a result, the Quick Access Section should be running properly.

File Explorer


For more information about Microsoft Technology, check out our partner page.

You can find out  more details by visiting the link below:

Microsoft Windows Servers

Problems with Hosted Network

Known Personal Area Network / WiFi Sharing problems:


Windows has encountered an error initializing hostednetwork. (CF001006)

Virtual Router Error

netsh wlan start hostednetwork
The hosted network couldn’t be started.
A device attached to the system is not functioning.


The problem is caused when VMware Virtual Ethernet Adapter for VMnet1 / VMnet0 (from VMware Workstation) are active.


  1. Disable all VMnet virtual adapters.  Restart computer.
  2. Change the Wifi mode from Wi-Fi Access Point to something else. Change it back. This alters the hostednetwork settings.

Related problem

Internet Connection Sharing

SharedAccess_NAT 34005
The ICS_IPV6 was unable to allocate bytes of memory

ShareAccess_NAT 34001

The ICS_IPV6 failed to configure IPv6 stack.

Network Resolution

Try changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters\DisabledComponents (DWORD) to either 0x00000000 or 0xFFFFFFFF.

0x00000000 to enable all IPv6 functionality

0xFFFFFFFF to disable all IPv6 functionality

See our Services Page for more information!

For more information on VMWare, visit the link below:

Exchange 2007 services won’t start after Windows Update


HOWTO: Resolve Windows Update Issue


Official Windows Logo - Windows Update


This particular problem is caused by installing KB2756918 on a Server 2003 x64 machine running Exchange 2007. I don’t know the specifics, I just know how to fix it.

Windows Update Solution:

First you have to rename two “machine.config” files located in C:\windows\\framework64\v2.0xxx\config and C:\windows\\framework\v2.0xxx\config Rename machine.config to machine.config.old and copy machine.config.default in the same directory and rename the default config file to “machine.config”. Make sure to do this in both directories.

Reboot the server and your Exchange transport service should be able to start.

If your OWA doesn’t come back up and you get a message “service unavailable” even after a few iisreset commands you may have to re-register .net v2.0 with IIS. To do this enter the aspnet_regiis.exe command with the –I flag. Here’s an example for my directory structure.

C:\windows\\framework64\v2.05727\aspnet_regiis.exe –i

After that, restart IIS and check to see if your OWA is working. Send a couple test messages and make sure to hide KB2756918 from being installed on the server to avoid this issue in the future.

For more ways we can help take a look at our IT Support Site.

Unattend.xml to Sysprep your Image and not disable local Administrator

Unattend.xml to Sysprep your Image and not disable local Administrator

Tools needed

  • Windows system Image Manager “This is part of the WAIK installs”
  • Windows 7 Install.wim, Boot.wim (Found on your windows 7 installation media in the Sources folder)

Note: copy these files locally and remove the “Read-Only” Attribute from each .WIM

Building your answer file using Windows (SIM)

Be sure to open this application by using the “run as administrator” option

    1. Open the “Install.WIM” using the “File and Select windows” option within Windows (SIM) Figure 1

Note: This step may take a bit to mount this image file (You will be prompted for the Windows version you want to build the file for… Once complete you will see the Components and Packages retrieved from the WIM file.

Figure 1

    1. Next you will need to open a “New Answer File” Under file option in figure 1 and add the following components in the order shown
      1. Generalize
        1. Add amd64_Microsoft-Windows-Security-SPP_6.1.7600.16385_neutral – right click and add to Pass 3 Generalize
          1. Change Setting to SkipRearm to value 8 Pix 2 (1)
      2. Specialize
        1. Right click and Add amd64_Microsoft-Windows-Deployment_6.1.7600.16385_neutral – right click and add -RunSynchronous- pass 4 Specialize
          1. Change the following settings to reflect the Screen ShotPix 3 (1)
        2. Next add SkipAutoActivaction using – Right click and add pass 4 Specialize- amd64_Microsoft-Windows-Security-SPP-UX_6.1.7600.16385_neutral
          1. Change the following setting – SkipAutoActivation to the value TruePix 4 (1)
        3. Next add amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral – click and add pass 4 Specialize (Note you can remove the sub components that are not needed)
          1. Change for the following settings to reflectPix 5 (1)
            1. (Please view TimeZone settings hereNote:later we will input License names etc into a different component
      3. oobeSystem
        1. Right click and Add Pass 7 oobeSystem – amd64_Microsoft-Windows-International-Core_6.1.7600.16385_neutral
          1. Fill in en-us in the ones in picturePix 6 (1)
        2. Right click and Add Pass 7 oobeSystem – amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral
          1. Fill in the following with your InformationPix 7 (1)
          2. AutoLogon Section
            1. Enter the followingPix 8
          3. Password Section
            1. Enter your PasswordPix 9
          4. FirstLogonCommands
            1. Right click and add new Synchronous commandsPix 10
            2. Right click and add new Synchronous commandsPix 11
              1. You will now have the following under “FirstLogonCommands”Pix 12
          5. OOBE
            1. Next Select OOBE and adjust the followingPix 13
          6. UserAccountsPix 14
            1. AdministratorPassword
              1. Add the value you want the password to be My example shows Password123!Pix 15
            2. This time we will right click Local account and (Insert New Local Account)Pix 16
              1. Fill in the unique values you needPix 17
            3. Your tree in the end should look like the following ScreenShot if you added what I’ve discussed above

Pix 18

Finally Validate your Answer file from a option under “Tools” and Save your Answerfile naming it unattend.xml for testing

  1. Once you have everything configured correctly, Copy or move your unattend.xml file to : C:windowssystem32sysprep
    1. To test open your command Prompt as an “Administrator” and change to the directory path above. Execute the following command sysprep /generalize /oobe /unattend:unattend.xml /shutdown
    2. Once your machine is turned back on it will go through the boot up process with a Sysprep that will prompt you to ONLY change the computer name. It will then Auto-login as the Administrator account so you can proceed with your final steps.


This walk-thru guides you through steps to do the following

  • Enable Administrator Account with a specific Password
  • Insert you Volume License
  • Name your Computer
  • Remove the need for a multi-part interaction

For assistance with your project, please see our pages for Microsoft System Imaging.

SOLVED: Can’t use Remote Desktop from Remote Web Workplace IE9

Windows 8 can’t use Remote Desktop from the Remote Web Workplace with IE9

This is a known issue with IE9 the following resolutions:

  1. Open Internet Explorer
  2. Navigate to your RWW site
  3. Click Tools – Internet Option
  4. Next click the Security Tab
  5. Then click Trusted Sites
  6. After that, click the Sites button
  7.  Next, click Add
  8. Finally, click Close
  9. In the Address area of IE click the compatibility button as shown in the image

CompabilityModeButton IE9

For more solutions like this visit our IT Support Site!

For more information about some of our other services, visit the site below:

Windows 8 Prompts for SharePoint Login Continually


Internet Explorer & SharePoint 
SharePoint Internet Explorer


As our team gets new computers more of us are on Windows 8 and we noticed that Internet Explorer continually prompts for authentication when going to our SharePoint site. We have a solution to end this annoyance!

Internet Explorer Solution:

  1. Open IE
  2. Navigate to your SharePoint Site and login
  3. Click the Cog icon – Tools and choose internet options
  4. Next, click the Security Tab
  5. Then, click Local Intranet
  6. After that, click the Sites button
  7. Then, click the Advanced button
  8. Click Add
  9. Finally, close your way out of the dialog boxes
  10. Tada!

I hope this helps you end a very annoying problem. I know I’m happier!

Check out our IT Support site for more ways our team can help you do your job quickly and efficiently.

For more information about SharePoint, visit the site below:

Server 2012 Windows 8 Logon failure: User not granted logon type

Logon failure: the user has not been granted the requested logon type at this computer Server 2012 Windows 8

In server 2012 and Windows 8 you may encounter a similar error that will not let you do simple tasks with windows features and programs. In our case it was starting a virtual machine in Hyper-V. It also affects SharePoint and Exchange as well.

To remedy this issue you must modify a local group policy. Open up gpedit.msc. Drill down Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment. Under Log on as batch job click the add user or group. Add the account you are currently logged in as. If the button is greyed out then you need to change this in the “Default Domain Policy” or “Default Domain Controllers Policy” as it is set to Deny log on as a batch job and overrides local policy. Once completed apply and open a command prompt. Run gpupdate /force. Once this is complete you will no longer get the error.

This problem will reoccur often. Each time you see it, you must remove yourself, apply, add yourself again, apply again, run gpudate /force.

Microsoft is aware of the issue and hopefully working on a resolution as the workaround is rather inconvenient at times.

Contact our Network Support team and see our Hyper-V, SharePoint, and Outlook Exchange pages for more ways we can help you!

Windows 7 Remote Desktop port 3389 Stopped Working

Recently we had remote desktop stop working on a few of our clients Windows 7 Pro machines. After patching together some resolutions, we have come up with a surefire way to remedy the problem.

  • Uninstall update(s) KB2621440 and/or KB2667402
  • Reboot
  • Run sfc /scannow from a command prompt to check for file corruption
  • Reboot if necessary
  • Verify that rdpcorekmts.dll exists and is atleast version 6.1.7601.xxxx (if it is not then copy it over from a working machine)
  • Export this registry key from a working machine and import it into the broken machine HKEY_CLASSES_ROOTCLSID{18b726bb-6fe6-4fb9-9276-ed57ce7c7cb2}
  • Reboot
  • Then, export these registry keys from a working machine and import it into the broken machine HKLMSYSTEMCurrentControlSetControlVideo{DEB039CC-B704-4F53-B43E-9DD4432FA2E9} and HKLMSYSTEMCurrentControlSetservicesRDPDD
  • Reboot
  • Test Remote Desktop to see if it is working. If it is, then the problem is fixed. If it is not, continue with the following steps
  • Check for and register the following .dlls in C:windowssystem32: rdpcore.dll, rdpcorekmts.dll, and remotepg.dll (in command prompt: regsrv32 rdpcore.dll) (replace any missing .dlls in the directory)
  • Reboot again
  • The problem should now be resolved and you should be able to reinstall the update/updates

Our Network Team is happy to help you with any troubleshooting problem, big or small. Call us today!

SOLVED: Windows Activation Error 0x800723B


Windows Activation Error 

After installing Windows 8 Enterprise or Upgrading to Windows 10 Enterprise and attempting to activate, you may receive an error message stating:

“Windows can’t activate right now. Try activating Windows later. If this issue persists, contact your system administrator or technical support department for assistance”

The error details shows: 0x8007232B – (DNS Name Does Not Exist)


After researching the error, it became obvious that this has been around for a while, and it is most often caused by the product key being invalid. Windows 8 and Windows 10 Enterprise do not request the product key during installation, and therefore the activation error occurs. On Windows 8. there is no obvious way to change the product key, and it really just is as simple as entering a valid product key.

Many of the recommended solutions I found require command line interaction from an elevated (run as administrator) command prompt. There is a simpler way to enter a new product key.

Windows Activation Error Solution:

1. From the Windows 8 Metro Screen or Windows 10 Start Menu, type: SLUI 3 (note the space) to automatically search for the product key utility.

3. Opening this will bring up the product activation window with a field for entering a new product key.

4. Enter the new product key and activate Windows 8 or Windows 10 Enterprise (Note that on Windows 10 Enterprise, you could just go to Settings>search for “Activation”, open “Change Your Product Key”, click “Change Product Key” and enter the new key.)


This issue has also been reported on various Windows 7, 8, and 10 releases, including the Gold Partner releases and MSDN releases. Although I haven’t tested it personally on all of these, this solution should still apply.

If you are still experiencing activation errors, confirm that you are not attempting to install a KMS (Key Management Service)
copy. The activation of a KMS volume licensing version of the OS requires a KMS licensing server to be running on the local network (not the most common approach for many businesses) and attempting to install this version without the KMS server can also produce this error.

Acumen Consulting provides computer and network support services to enterprise, small and medium sized businesses. If you require further assistance, please contact us and we will be happy to help you resolve error 0x8007232B -DNS Name Does Not Exist during Windows 8 or Windows 10 Enterprise activation.

For more information on Windows, click on the link below:



An error caused a change in the current set of domain controllers


An error caused a change in the current set of domain controllers

In a Windows Domain with Exchange, it is possible that after demoting a domain controller Exchange 2010 Management console will not open properly.

You may see repeated error messages similar to “An error caused a change in the current set of domain controllers.

It was running the command…”. The error repeats regardless of opening and closing the MMC, logging off and on, or restarting the server.

Resetting the configuration domain controller is still possible within the MMC.

But be aware that does not fix the problem.

Domain Controllers Solution:

A solution that has worked to solve this problem is to delete the file “Exchange Management Console” in C:\users\[user]\AppData\Roaming\Microsoft\MMC

After deleting this file, reopen the Exchange Management Console and the file will be recreated.

If you found this useful please visit our IT Support Home Page at Acumen and see other ways we can help you!

Windows 7 Phone – Setup Incomplete

Windows 7 Phone

Window 7 Phone Problem:

Recently, I was issued a new Windows 7 phone.  Being the owner of one previously, I was already familiar with the OS and had a Windows Live ID that I entered when the sales rep asked me.

The phone was just out of the box, and as soon as I entered my information, the battery died.  After attaching it to the A/C adapter, the phone came on and acted the way I expected it to with no additional setup questions.

The issue arose when I attempted to connect it to my PC in order to install the updates to it.  The Zune software recognized the phone, but soon prompted me with “Phone Setup Incomplete. When you’re ready, disconnect from the computer and complete the remaining steps on the phone.”  When I unplugged my phone, there were no additional prompts on the phone.  Reconnecting to the PC yielded the same result, as did

Windows 7 Phone Solution:

· Connecting to another PC running the Zune software

· Soft-reboot the phone (shutting it down via the power button)

· Hard-reboot the phone (removing the battery)

Now, in the meantime, the phone was is all other ways operating properly.  It was syncing apps that I had downloaded onto my other phone via my Windows ID account.  It called out and connected to our WIFI and so on.  All that was missing was the ability to connect to the Zune software (which, in addition to synching media, is the Windows Phone 7 method of installing updates).

The final solution was to take the phone settings back to factory.  I did this on the phone by going to Settings -> about and then selecting “reset your phone.”  After that, the phone prompted me for my Windows ID again as it started back from the beginning.  Upon attaching the phone to my PC, updates started and a couple of hours later, my phone was done and I was back in business with it.

See our Network Support page for more ways we can help you!