Month: October 2020

Case 1: After installing the 20H2 update. my computer lost all sound. 

Went to task manager–under System Devices a red X on Intel Smartsound SST OED. Normally in Task Manager under “Sound, Video and Game Controllers” there are five entries including Realtek HD Audio–all of them completely disappeared except the two Nvidia entries.

Called support–we tried reinstalling the latest sound drivers from HP (I have a 17″ Omen Laptop) and it said the drivers would not support this version of Windows.

Finally the support guy had me roll back the update. Back up and running now on version 2004.

Case 2: My Windows didn’t start with blue screen after installing Windows 10 version 20H2. I must re-install previous windows 10 version.

Case 3: Can’t install Windows 10 version 20H2.

Resolution: you may need to run SFC /SCANNOW and DISM.exe /Online /Cleanup-image /Scanhealth && DISM.exe /Online /Cleanup-image /Restorehealth

Case 4: I get this message “Unable to complete updates. Undoing changes” when installing Windows 10 version 20H2.

Resolution: ejecting external drives either external SATA or USB, caused by windows defender MsMpEng.exe. 

Or For now, as a workaround, I had to add the external drives to the exclusion list to avoid the ejection block.  In my case the external drive has the letter E:\, this can vary in different machines or if there is more than one external drive.

Case 5: You may receive, “Windows can’t verify the publisher of this driver software” when installing Windows 10 version 20H2. It causes by incorrect device driver.

Case 6: I can’t update my windows, and every time I go to windows update, it says that something went wrong and try to re-open settings.

Resolution: Download and install Windows Update Assistant. This step by step video may help:

Situation: When attempting to activate office 365, you may receive this message: Error Code 80090034.

Case 1: The client’s domain name is compnayname.mydomain,com and email address is username@mydomain.com. When he setup a new laptop, the laptop takes username@compnayname.mydomain.com as email address. To fix this problem, go to Settings>Account>Access work or school to delete username@compnayname.mydomain.com. Re-assign in using username@mydomain.com.

Case 2: Try this method:

Go to the registry editor (Win+R; regedit)

go to HKEY_CURRENT_USER -> Software -> Microsoft ->Office -> 16.0 ->Common -> Identity

Inside “Identity”, create a new REG_DWORD value called “EnableADAL” and leave the value at 0

Restart the PC and try again to login from Office 365. In my case, the logon screen was now different and it worked perfectly.

case 3: Repair the Office 365 under control Panel>Uninstall programs.

Case 4: Re-install Office 365.

Case 5: Solution was to set this registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb\ProtectionPolicy = 1 (DWORD)

Case 1. The client’s domain name is companyname.mydoamin.com, he doesn’t know which is the domain name. If their have correct name resolution or DNS setup, either pre-windows 2000 name compnayname or GQDN companyname.mydoamin.com should work.

Case 2. In above case 1, only pre-windows 2000 name compnayname works, GQDN companyname.mydoamin.com doesn’t. The reason for this, it could be the mydoamin.com is the public domain name. If you ping mydoamin.com and get a public IP address. You may not be able to join the domain use the public domain name, like mydoamin.com. In this case, you may create A record in your DNS and point the mydoamin.com your local private IP address. Otherwise you must use pre-windows 2000 name like compnayname in out above example.

Case 3. in above case 1 and 2, pre-windows name doesn’t work also. one resolution is install WINS server on your DC.

Case 4: in above case 1 and 2, none of pre-windows name or FQDN works. In this case check the DNS settings. In one of our cases, the client use their router as DNS server. it is recommended to setup DNS on the DC and each client use the DC DNS as primary DNS server.

Case 5. in other case, the client setup a laptop using WiFi. However, the WiFi uses different IP range from wired. Using Wired connection fixes the problem.

Case 6. Use network ID instead of Change to join the domain.

7. Using hosts or/and lmhosts.

Situation: The use login this morning, all icons in the Desktop are missing and it is blue screen.

Troubleshooting: 1. Enable “Show desktop icons” by right-0clciking on the blue screen and go to View.

2. Enable the Desktop Icons Visibility

• Right-click on blue screen and select “Personalization”.
• Select the “Themes” tab from the left pane.

• Click on “Desktop icon settings” to open the settings.

• Select the icons you want to show on the desktop or click on “Restore Default”, and then click on “OK” to save the settings.

3. Disable the Tablet Mode

• Open the Settings> System to open the system settings.
• On the left pane, click on “Tablet” and make sure you don’t use Tablet Mode.

Situation: the client just add an image to Outlook Profileby following this article;

How to setup or change the profile image on Outlook

. However, the image doesn’t show up.

Troubleshooting: Normally, it takes 48 hours to update and will show.

Situation: When a new user login Mitel Connect, she receives this message: Either your username, password, or server didn’t match.

Troubleshooting: 1. Since the Domain already has the domain name entered, don’t use domain in username. The correct username is username. If you enter domainname\username, that may not work.

2. Sometimes, email as suername doesn’t work.

3. Also make sure you sync the AD under General.

Situation; The client has a Windows 2012 R2 as Mitel phone server. After they start the server, they can’t ping or RDP into it.

Troubleshooting: 1. Ping server, it back with 169.x.x.x IP address.

2. The NIC 1 IP address should be 10.0..40. However, it was assigned 169.x.x.255 IP address which is  auto-configured addresses.

3. We try to use DHCP to assign the IP address, but it doesn’t work. It still shows 169 IP address.

4. Then we reset IP address to 10.0.0.40, but it doesn’t take it and still show 169 address.

5. We fixed the problem by connecting the cable to NIC 2 and assign IP 10.0.0.40. I also remove the 10.0.0.40 from NIC.