After a bit more troubleshooting, I found when Outlook froze up, if I opened a File Explorer Window it would unfreeze Outlook and I could once again use. 

Another item I noticed was Outlook seemed to freeze when I used my mouse scroll wheel instead of the scroll bars on the previewed Excel document. I tried my hypothesis a couple times and sure enough, each time I scrolled the previewed Excel document with my mouse scroll wheel Outlook would freeze up.

Troubleshooting Steps I tried:

1. I installed the latest Office updates.
2. I opened Outlook in Safe Mode.
3. I made sure all Add-Ins were disabled. 
4. I ran Outlook as an Administrator
5. I disabled all Preview Handlers in Outlook and then re-enabled. 

The above troubleshooting steps did not resolve my issue. Here is the solution that finally worked for me. 

Step One: Open Windows 10 Settings (WinKey + I)

Step Two: Go to Devices > Mouse 

Step Three: Turn Off “Scroll inactive Windows when I hover over them” 

The Windows 10 feature “Scroll inactive Windows when I hover over them” is supposed to allow you to scroll through side-by-side Windows without having to click it to put focus on each Window. You can just hover over the Window and scroll.

Apparently, the “Scroll Inactive Windows When I Hover Over Them” doesn’t work well with Outlook.

I hope this helps. If it did, please sound off in the comment section below. This was posted by techspeeder. 

If this helped you, consider helping me, by using my Amazon Affiliate link to keep this blog active and to buy an occasional coffee. 

The “Open in Edge” button can be frustrating and confusing to users. Here are the steps to disable the “Open in Edge” button.

Open Internet Explorer and click the Gear icon in the top right hand corner of your browser.

Go to Internet Options

Then Go to Advanced and then check the box: Hide the button (next to the New Tab button) that opens Microsoft Edge. Save your Settings.

Close Internet Explorer and reopen. Your “Open Edge” icon should be gone!

This was posted by techspeeder. Please let a comment below if it helped! 

However, the adapter would always assign the external DNS server first and then the internal DNS servers as secondary. 

The VPN client couldn’t locate local resources on the network over the VPN.

In my troubleshooting this issue, I found that this is actually a bug. Here is what I did to fix the issue. 

Step One: On your RRAS server open the Registry to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RemoteAccess\Parameters\IP

Step Two:  Make a Dword32 Key and Name it SuppressDNSNameServers. Give the value of the key 1.

Step Three: Restart the RRAS service on the server.

You should be set! If the above doesn’t work, try rebooting your server and trying your VPN client again. 

Thanks for reading! Please consider subscribing to my blog. This was posted by techspeeder. 

P.S. This also worked on my personal Windows 10 1607 computer. 

Step One: 

• Change the value of HKEY_Users/<UserProfiles>/ControlPanel/Keyboard/InitialKeyboardIndicators to 2147483650 for ALL USERS profiles not only for .Default. 

Step Two: Once the above edits in the Registry have been completed. Shutdown the computer.

Step Three: Turn on your computer and wait for login screen (NumLock is still off). Log into your computer.

Step Four: Enable NUMLOCK and shutdown your computer.

Step Five: Turn on your computer. NumLock should now be enabled.

Let me know if the above solution works for you. Hat Tip to this Reddit Thread. 

I hope this helped. If it did please let a comment below! You can follow me on Twitter and subscribe to my YouTube Channel. This was posted by techspeeder.

I am running the Windows Insider build,so there is a chance that some of the features won’t make it into the final Anniversary Update release. Enjoy!

This was posted by techspeeder.

I tried these troubleshooting steps and none of the below worked.

• Started Chrome in Incognito Mode and typing was just as delayed
• Created a new Chrome profile – same issue
• Reinstalled Google Chrome – no go
• Tried Mozilla Firefox and Internet Explorer – they were both fine
• Checked Chrome browser extensions but only had LastPass & AdBlock Plus Installed
• Disabled various flags under Chrome://flags – didn’t help
• Checked to make sure the browser wasn’t starting in compatibility mode – it wasn’t
• Tried starting the browser in compatibility mode – that didn’t work either
• Disabled Hardware Acceleration in Chrome – No Change
• Disabled Chrome from running in the background after the browser is closed
• Removed Internet filtering software on computer- same trouble

I searched high and low on the Internet for an answer to this issue. However, I could find nothing that worked.

After all the above troubleshooting, I was convinced it was a process in Windows that was creating issues. I started by killing one process at a time and then typing in Google Chrome. After killing the iDrive process, for iDrive online backup, I tried typing in Google Chrome – everything was fine. I started iDrive backup again and once again my typing in Chrome was delayed.

I updated the iDrive application to the latest version and it seemed to have fixed the issue. If this issue returns again, I may need to uninstall iDrive and install a different online backup program.

I really can’t explain why this fixed the issue. I know the fix above may not solve your slowness issues in Chrome. If there is one person out there that this article can help, it will be worth this blog post. I will post some links below to some other articles that have Google Chrome troubleshooting tips that may help you.

http://www.tomsguide.com/answers/id-1951169/google-chrome-slow/page-2.html

https://www.reddit.com/r/chrome/comments/2bslbg/reddit_on_chrome_is_going_slow_typing_lag_is/

Please let a comment below if this post helped you, thanks. This was posted by techspeeder.

Typically, I join the computer to the domain using the Windows Server Essentials connector tool. Here are the steps I use below.

Step One: I went //servername/connect and installed the connector software. I rebooted the computer when I was prompted to do so.

Step Two: The computer rebooted and started booting into a _clientsetup_$ profile. The computer took a minute or two but it logged into the _clientsetup_$ profile. I was then prompted to enter the user’s credential’s to connect the computer to the domain.

Step Three: I entered the credentials, and then I selected “Setup this PC for myself”. Instantly, the connector software froze and said: “Windows Server Essentials Connector” has stopped responding, end program. The Connector software closed but the computer kept me logged into the _clientsetup_$ profile until I rebooted the computer.

I then logged into the computer. The computer was joined to the domain but the Connector software was not installed.

I thought this may have been a one-off issue so I tried joining the computer again. Once again, I was greeted with “Windows Server Essentials Connector” has stopped responding. I will list below all the things I tried -none of them worked.

• I tried to join the computer to the domain with the admin credentials instead of the user’s credentials.
• During the Connector software setup, I selected “Setup this PC for myself and others” instead of “Setup this PC for myself.
• I checked Event Viewer. It said clientdeploy.exe has stopped working. Right before that error, I got a .Net framework error as well. I ran the Microsoft .Net Repair Tool. The .Net repair tool didn’t fix my problem, so I turned off .Net framework in “Turn Windows Features On or Off” in Windows. That didn’t work as well.
• Installed the Windows Server Essentials R2 Connector from Microsoft’s website.
• Right-clicked on the connector file and “Ran as an Administrator”
• Connected the laptop via an Ethernet connection (instead of wireless) and ran the wizard.
• I joined the domain manually and then tried to run the Connector software. It still failed.
• I created a new local admin profile and ran the Connector wizard from that profile.
• I rebooted the server.
• Disabled IPv6 on the laptop- we thought maybe there was a conflict
• Renamed the laptop multiple times
• I checked the server. The computer showed up under the devices tab in the dashboard as being on the domain.  However, the computer showed offline and the server didn’t know what OS was installed or anything about the client.

I decided to check the Connector software’s log and see if I could learn anything. I browsed to C:\ProgramData\Microsoft\Windows Server\Logs folder. I opened the log and found something very interesting. This is what the log read:

[3704] 160419.115344.2661: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-555])
[3704] 160419.115344.5319: ClientSetup: !!!FATAL!!! Unhandled Exception: System.ComponentModel.Win32Exception (0x80004005): No mapping between account names and security IDs was done
at Microsoft.WindowsServerSolutions.ClientSetup.NativeMethods.LookupAccountSid(String computerName, SecurityIdentifier sid)
at Microsoft.WindowsServerSolutions.ClientSetup.User.AddRoles(UserRoles userRoles)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.m_wizardPageSetupForMyselfOrOthers_

I found this error had to do with a user account issue. I found on Microsoft’s MSDN website that the S-1-5-32-555 SID is a remote desktop users local group. Apparently, the connector was running into some problem with the remote desktop user group.

After doing some searching, I found a forum thread that was detailing the exact same thing – except those computers were running Windows 8. The forum mentioned that the computers that were having issues were mostly computers that had been upgraded from Home to Pro. This stirred my thinking and I remembered that this laptop had been upgraded from Windows 10 Home to Windows 10 Pro.

I am quoting this from another forum thread on Technet.

Based on the ClientDeploy.log above, it looks like it successfully looks up the local [Administrators] group (SID [S-1-5-32-544]) and successfully adds the “Me” account (SID ending in -1116) to that group.  It looks like it blows up when it tries to get the name for SID [S-1-5-32-555], which is the well-known SID for local group “Remote Desktop Users”.

Coincidentally, I noticed that in looking at the Computer Management console, the Windows 8 Pro computer (“moved up” from Windows 8) doesn’t have that local group for some reason.  A second Windows 8 Pro computer that I have, which was Windows 8 Pro out of the box, does have that group.  Thus, at this point, I’m still suspecting a bug in the process that “moves up” Windows 8 to Windows 8 Pro.  While it may or may not be related to this specific problem, why would the “Remote Desktop Users” local group (as well as several others that should be present in Pro) be missing?

Microsoft later addressed the Windows 8 Home to Pro upgrade issue with this update rollup. I know the article I referenced is dealing with Windows 8, but I believe this is also an issue with Windows 10. Somewhere in the upgrade process from Windows 10 Home to Windows 10 Pro the “Remote Desktop User” local group got missed.

I ended up joining the domain manually and just skipping the Connector software for now. If anyone has run into this issue as well, please let me know in the comments below. Better yet, if someone knows a fix or a workaround for this issue that would be awesome! I hope Microsoft addresses this bug in an upcoming update like they did with Windows 8.

I found this article that may fix the missing user groups after a Windows 10 Home to Windows 10 Pro upgrade. I didn’t have time to test this solution but it may be worth a shot.

This was posted by techspeeder.

This is the latest bug I found with Windows 10 Version 1511. In Windows 10 offline files are not indexed or searchable in the Windows 10 start menu. Let me explain how a lot of small companies are setup and how this impacts us.

Most small networks have some version of SBS or Server 2012. A lot of IT admins, including us, using the folder redirection group policy to redirect the users’ documents to the server. This essentially gives the workstation a “backup” for its documents and also allows a user to access their documents on multiple devices.

On each device we set the redirection folders to also be offline files. This allows the user to go outside the network and still have their redirected documents with them. This works absolutely beautiful with Windows 7 – you would think it would work great Windows 10 as well, but NO it doesn’t.

I verified this has happened on multiple computers and different customers. When you set the documents to be offline files and redirected, Windows will “index” the offline files – but it really doesn’t. A quick search in the start menu will come back absolutely empty. You can search all you want with the new “Better” start menu and it will not return even one redirected , offline file. Good Job, Microsoft!

I knew we couldn’t be the only company that uses redirected folders and offline files, so I did some checking on Google. Sure enough I found this forum thread with other users that have the exact same problem.

I would like to hear from you if you are experiencing the same problem. If you are experiencing the same problem, please post of this forum thread and comment below if you have found any fixes or work around.

In the meantime, I will keep a close eye out for any fixes that come along. As far as for the users that already upgraded to Windows 10, sorry no searching Windows 10 offline files for you – yet!

This was posted by techspeeder. Please follow me on Twitter and subscribe to my YouTube Channel.

After you hit CTRL + ALT + DEL to login into your domain computer, you can find your computer name by simply doing the following. Where you normally enter your username simply type .\ . This will list the computer name below the password field. Pretty cool aye? This simple trick works on Windows 7 and Windows 10. To see the domain again, you simply erase .\ and you will see your domain name. 

If this tip helped you out, please consider subscribing to my blog and check out my YouTube channel. If you have additional tips or questions, please leave them in the comment section below. This was posted by techspeeder.

“We couldn’t upgrade your edition. Try upgrading your edition of Windows again or contact your system administrator or Microsoft. Error code: 0x0 “

As you can see, that error code doesn’t give you much information. After multiple attempts, I decided this wasn’t a fluke issue and decided that there much be some software issue.

Here is how I resolved this issue. I’m not sure which troubleshooting step actually solved the issue but the upgrade went smoothly after I did the following.

Step One: I uninstalled McAfee Antivirus software. I have never liked McAfee so I decided I would start there.

Step Two: I disabled all applications from starting up. Here is the list of applications I disabled from startup.

BlueTooth Tray Application

Catalyst Control Center

CyberLink MediaLibrary Service

CyberLink Virtual drive

HD Audio Background Process ( Three of These)

Lenovo Utility

McAfee

Microsoft OneDrive

Realtek HD Audio Manager

Synaptics TouchPad

I started the Windows 10 Pro upgrade again and this time we were successful.

I hope this tip helps you. If you have had a similar experience, please post a comment below and follow me on Twitter.

This was posted by techspeeder.