Windows Update causes network problem

Situation: Whenever the client installs Windows update, it causes network traffic problem and makes internet slow.

Troubleshooting: We recommend to setup WSUS server to download the updates and distribute them to all computers .

Also, Microsoft recommend this:

The following group policies can help mitigate this:

Other components that reach out to the internet:

Many Windows and update problems can be fixed by running SFC and DISM

If you experience a Windows problem or Windows update problem, you may try to run System file check (SFC) and to fix it.

To run a system file check (SFC)

Go to start>Type CMD

Right click and run as Administrator

Type sfc /scannow

It may shows one of three possible results:
Windows did not find any integrity violations (a good thing)

Windows Resource Protection found corrupt files and repaired them (a good thing)

Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)  If you get this message run DISM as described below

To RESTORE health (recommended)

Use DISM /Online /Cleanup-Image /RestoreHealth to scan the image for component store corruption, perform repair operations automatically, and records that corruption to the log file.  This generally takes 15-30 minutes depending on the corruption and size of the partition.

Note: 1. You may have to run this up to 3 times to fix all the problems.

2. After running DISM it is a good idea to re-run SFC /scannow to make sure all the issues were fixed.

3. If you get the error message “cannot find source files”you need to have an ISO file mounted and need to specify where it is located with the below command. The ISO must be exactly the same version as the running OS.  An ISO of 10586.0 will not repair a running system of 10586.35 because it has additional updates and files.

Can’t turn on Thinkpad X1 Yoga

Situation: The client has a Thinkpad X1 Yoga with full charged battery. He can’t turn on the laptop with power plugs in and full battery charged. When pressing the power button, the power light is not on. When you plug the power on, the power light on for sends and disappears.

Resolution: reset battery

1   Remove Laptop bottom cover.

2   Disconnect two battery connections.

3  Disconnect coin-cell (CMOS) battery.

4. Disconnect the cable in the power button.

5. Press power button a few times to drain capacitors

6. Put all connections back and try again.

Hyper-V virtual machine may not start with “General access denied error (0x80070005)”

Situation: The client is running Windows 2016 Hyper-v and moves the VM to different drive. Now, they can’t start the VM.

Troubleshooting: 1. They should not us copy and past to move the VM. They should use export.

2. Hyper-V virtual machine may not start, and you receive a “‘General access denied error’ (0x80070005)” error message Every Hyper-V virtual machines has a unique Virtual Machine ID (SID). If the Virtual Machine SID is missing from the security permissions on the .vhd or .avhd file, the virtual machine does not start, and you receive the “‘General access denied error’ (0x80070005)” error message that is mentioned in the “Symptoms” section. Please refer to this article:

Google Custom Search HyperV virtual machine may not start, and you receive a “’General …support.microsoft.comhttps://support.microsoft.com/…/hypervvirtual-machine-may-not-start-and- you-receive-a-general-access

3. There are two ways to fix the problem. The easy (but completely insecure) fix is to give Everyone full control of the virtual hard disk file. The “correct” fix it to give read and write access to the virtual machine’s SID.

You can find the virtual machine’s SID by using the Get-VM cmdlet in PowerShell. For a VM named New Virtual Machine the command would be:

Get-VM 'New Virtual Machine' | Select-Object VMID

4. Update the Permissions

The solution is to give the SID Full control of the VHD using the command line.

Tip: Rather than type (or mistype) the SID by hand, cut and paste it from the event log message or from the XML file name in the Virtual Machines folder.

The command:

icacls <Path of .vhd file> /grant "NT VIRTUAL MACHINE\<Virtual Machine SID>":F

Note that there is no space before the :F. For example:

icacls "D:\Virtual Machines\VM01\Virtual Hard Disks\DRIVE01.VHD" /grant "NT VIRTUAL MACHINE\6B78D45F5-71DF-4725-B4B2-E651800BE80EF":F

Once that permission has been added, you should be able to start the virtual machine.

5. Updating the NTFS level permissions: 1.  On the destination server, Right-click on the shared folder and select Properties. 
2.  Select the Security tab. 
3.  Click Edit button and click the Add button in the permissions dialog box. 
4.  Click Oject Types and select Computers if not already done and click OK
5.  In the dialog “Enter the object names to select” provide the name of Hyper-V host machine and click Check Names
6.  With the Hyper-V host machine name select, click Allow by “Full control” and click OK

Updating the share level permissions:1.  On the destination server, Right-click on the shared folder and select Properties. 
2.  Select the Sharing tab. 
3.  Click Advanced Sharing…
4.  On the Advanced Sharing dialog, click Permissions  and then Add. 5. Click Oject Types and select Computers if not already done and click OK
6.  In the dialog “Enter the object names to select” provide the name of Hyper-V host machine and click Check Names
7.  With the Hyper-V host machine name select, click Allow by “Full control” and click OK

Your credentials did not work. Your system administrator doesn’t allow the use of saved the credentials to log on to the remote Computer.

Situation: one of outside client cant login remote Desktop server with this error: Your credentials did not work. Your system administrator doesn’t allow the use of saved the credentials to log on to the remote Computer.

Troubleshooting: 1. Use other computer with the same username doesn’t have this problem.

2. We fixes it by do this:

“The reason why it wasn’t working was because Windows automatically stored the certificate in a “non-trusted” root store. Once it was moved RDP connected without prompting for credentials”

Other suggestions: 1. Change the group policy setting.

2. Security settings.

3. If the client is located the same LAN, change the network profile from public to private.

4. Make sure the company firewall allow remote session.

5. Edit Windows Security Policy.

6. Delete the credentials:

Go to Control Panel -> Credential Manager. You will see three sections:

  1. Windows Credentials
  2. Certificate-Based Credentials
  3. Generic Credentials

Remove the credentials from Windows Credentials and add it to Generic Credentials.

Server locks with Event ID 51: An error was detected on device \Device\Harddisk1\DR23 during a paging operation.

Situation: The client has Hyper-V server running Windows 2016. They can’t login server remotely or from the console. But all VMs run fine and they can access those VMs without any problems.

Troubleshooting: We use another server’s Computer Management and Service to connect to the Host server, every thing is fine except the Event ID: 51
Description:
An error was detected on device \Device\Harddisk1\DR23 during a paging operation.

We find they has external USB connect to the server. Unplugging the external USB and restart the host, everything works.