Category Archives: Fixes

Partitions may be missing after installing the Windows 10 Anniversary Update

The main thing to glean from this issue is “not try to recover or otherwise write data to the affected partition, nor should you format the partition”

From Microsoft – http://answers.microsoft.com/en-us/windows/forum/windows_10-files/partitions-may-be-missing-after-installing-the/ffafb34b-df6e-4c61-927d-babf29b46b87

Microsoft has received a small number of reports of partitions not appearing in File Explorer after installing the Anniversary Update. When viewing the partition in Disk Management, it appears as RAW, unallocated space.
Microsoft is aware of this issue and is working on a solution to be released through Windows Update. Any data you have stored on the affected partition is still there. We recommend that you not try to recover or otherwise write data to the affected partition, nor should you format the partition. We will update this thread when a patch is released. If you would like to be notified when this thread is updated, click the Subscribe button at the end of this post.
For up to days 10 days after installing the Anniversary Update, Windows includes the ability to “go back” or return to the previous build if you are experiencing this issue and do not want to wait for the patch to be released.

To uninstall the Anniversary Update:

  1. Open the Settings app.
  2. Select Update & security and then the Recovery tab.
  3. Under “Go back to an earlier build”, click the Get started button and follow the instructions.

(Note: If more than 10 days have elapsed since installing the Anniversary Update or the “Go back” option is otherwise not available; we ask for your patience until a patch can be released. Please check back on this thread for an update.)

Windows 10 may freeze after installing the Anniversary Update

More problems are brewing with reports that Windows 10 may lock up or experience unusual networking issues after installing the Windows 10 Anniversary update.

One of the first troubleshooting steps to take is to uninstall and re-install the networking drivers.

If this does not work, follow the steps noted here to rollback the update until a fix is released – http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-may-freeze-after-installing-the/5a60d75d-120a-4502-873c-8bfec65c82d0?page=1&auth=1

Method 1: Using the Recovery Console

  1. Restart your PC. When you get to the sign-in screen, hold the Shift key down while you select Power > Restart.
  2. After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced Options > Go back to the previous build. If you don’t see this option, try Method 2.

Method 2: Using the Settings app from Safe Mode

  1. Restart your PC. When you get to the sign-in screen, hold the Shift key down while you select Power > Restart.
  2. After your PC restarts to the Choose an option screen, select Troubleshoot > Advanced options > Startup Settings > Restart.
  3. After your PC restarts, you’ll see a list of options. Select 4 or F4 to start your PC in Safe Mode.
  4. Open the Settings app.
  5. Select Update & security and then the Recovery tab.
  6. Under “Go back to an earlier build”, click the Get started button and follow the instructions.

Windows 10 Anniversary Update and Windows Server 2012 R2 Essentials

If you are running Windows Server 2012 R2, and have Windows 10 Clients that will soon update to the Windows 10 Anniversary update, you should review the following links.

Susan Bradley’s blog on the manual steps required – http://blogs.msmvps.com/bradley/2016/08/11/windows-10-anniversary-update-and-essentials-r2/

Robert Pearman’s blog with some Powershell fixes – https://windowsserveressentials.com/2016/08/05/july-update-rollup-kb3172614-and-windows-10/

Reinstalling he Essentials Client Connector – Cannot download the package. Check these out – https://windowsserveressentials.com/2016/08/08/cannot-download-the-package-essentials-2012-r2/ and https://www.microsoft.com/en-us/download/details.aspx?id=40285

Installing the LAN Driver on Windows Hyper-V Server 2012 R2 on an Intel NUC 5i3RYH

I recently had to set up a Hyper-V server in a very small environment using an Intel NUC PC. The system installed well, but the LAN drivers would not install. Using information from the following two websites (https://jayrbarrios.com/2014/11/19/intel-nuc-d54250wykh-installing-lan-driver-on-windows-hyper-v-server-2012-r2/ and https://foxdeploy.com/2013/09/12/hacking-an-intel-network-card-to-work-on-server-2012-r2/), I was able to install the LAN driver properly.

  • Download the latest driver for the NUC for the Windows 8.1 operating system. The file should be called LAN_Win8.1_64_nn.exe
  • Extract the installer using WinRAR to the C:\TEMP folder.
  • Go to the following folder C:\TEMP\PRO1000\Winx64\NDIS64 and open e1d64x64.inf in Notepad
  • Remove the highlighted 3 lines.

  • Copy the following 3 lines

  • Scroll down to the next section and past them here

  • Save the inf file.
  • Run the following 3 commands from an Administrative command prompt.
    • bcdedit /set LOADOPTIONS DISABLE_INTEGRITY_CHECKS
    • bcdedit /set TESTSIGNING ON
    • bcdedit /set nointegritychecks ON
  • Reboot the server
  • Install the driver from an Administrative command prompt

    C:> pnputil -I -a C:\TEMP\PRO1000\Winx64\NDIS64\e1d64x64.inf

  • Click Install this driver anyway when prompted

  • The following messages should be shown.

    Processing inf : e1d64x64.inf

    Successfully installed the driver on a device on the system.

    Driver package added successfully…..

  • Run the following 3 commands from an Administrative command prompt.
    • bcdedit /set LOADOPTIONS ENABLE_INTEGRITY_CHECKS
    • bcdedit /set TESTSIGNING OFF
    • bcdedit /set nointegritychecks OFF
  • Reboot the server and check that the driver has install properly.

Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and WIndows Server 2012R2 Update Rollup all in a single package

Today, MIcrosoft announced the availability of a single update rollup package for Windows 7 SP1 and Windows Server 2008 R2. Some details for the rollup are as follows:

  • All security and non-security fixes since the release up to April 2016.
  • One installation package.
  • Optional install – not offered via Windows Update.
  • Monthly rollups after April 2016.
  • Security bulletins will continue to link to a direct update.
  • For Windows 8.1, Windows Server 2012, and WIndows Server 2012 R2, there will be monthly rollup updates.

Thanks, Microsoft, for listening!

To get the rollups, you need Internet Explorer 6 or higher (not Edge – since this is not an update package for Windows 10). Get the updates here – http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3125574

At this stage, other browsers are not supported, although Microsoft have hinted that the site will be updated in the next few months.

 

Outlook 2010 runs in Safe Mode after KB3114409

 

Microsoft released a bad patch on 9 December 2015, which caused Outlook 2010 to run only in Safe Mode. The fix for this is to uninstall the patch. Microsoft has already pulled this patch and is likely to release it again at a later time. I would suggest waiting at least a week before reinstalling this patch.

To fix this issue, perform the following steps to uninstall the bad patch.

  1. Close Outlook and All Microsoft Office Programs
  2. Open Control Panel
  3. Click on Programs. (Alternatively, you can search for View installed updates in the search bar at the top right corner of the Control Panel)

     

  4. Click on View Installed Updates

     

  5. Scroll down to the Microsoft Office 2010 section, and look for Update for Microsoft Outlook 2010 (KB3114409) 32-Bit Edition (or 64-Bit Edition).

     

     

     

  6. Click Uninstall

     

     

  7. Click the Uninstall button

     

  8. The patch will be uninstalled

     

  9. When the patch is uninstalled, click OK and close the Control Panel

 

 

Windows 10 Default Printer keeps changing

A “new” feature in the latest cumulative update for WIndows 10 automatically sets the default printer to the last used printer. This setting is turned on by default. This means that every time you use a printer, this printer becomes the default printer for the system.

While this might be a nice feature to have, it can potentially cause a waste of paper and some potentially “difficult” situations when documents are unwittingly printed to the wrong printer. ie, that receipt for the surprise birthday gift, or the 100 page draft document that was supposed to be printed to the paper optimiser print driver.

Fortunately, we can turn off this setting.

  1. Open up Printers & Scanners. Tip: Click on the Start Menu, and type “Printers & Scanners” in the search box.
  2. In the Printers & Scanners settings page, turn off the setting “Let Windows manage my default printer“.

PrintersAndScanners

Windows 10 support on Windows Server Essentials and Small Business Server

The Essentials Server team have released a blog post to highlight which client versions are supported on currently supported Windows Server Essentials and Small Business Server 2011. The blog post can be read here – http://blogs.technet.com/b/sbs/archive/2015/07/23/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os.aspx

Basically, if you need to connect a Windows 10 client to Windows Server Essentials 2012 R2, which is probably the most common scenario, you will need to perform a manual client connector installation. A fix for the server is scheduled to be released on 17 November 2015.

Another common scenario would be the joining of the client connector for a Windows 10 client to Small Business Server 2011. In this case, 2 lines need to be added to the XML file on the server, which is located at C:\Program Files\Windows Small Business Server\Bin\WebApp\ClientDeployment\packageFiles\supportedOS.xml. Add the following 2 lines.

<OS Architecture="9" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, AMD64" id="9"/>
<OS Architecture="0" RequiredProductType="1" RequiredSuite="" ExcludedSuite="512" SPMinor="" SPMajor="" Build="10240" Minor="0" Major="10" Name="Windows 10, x86" id="10"/>

Using Powershell to Start-Stop the SMTP Virtual Server

One of the most popular posts on this blog has been the blog on setting up an Internal SMTP Service for SMBs that need to send server reports and support emailing from Internal devices that have move to cloud based email services.

One of the issues with this service is that is occasionally stops. There does not appear to be any reason why it stops, but it does. Restarting the SMTPSVS service does not restart the service, because it is based on IIS6.

Good news! You can use powershell to script the restart of this service.

Open an Administrative PowerShell window.

To Start the SMTP Virtual Server, type the following:

$SMTP=[adsi]"IIS://localhost/SMTPSVC/1"
$SMTP.ServerState = 2
$SMTP.SetInfo()

To Stop the SMTP Virtual Server, type the following:

$SMTP=[adsi]"IIS://localhost/SMTPSVC/1"
$SMTP.ServerState = 4
$SMTP.SetInfo()