How to get rid of Chedot

If you are using your Google Chrome browser and suddenly notice a constant flickering after you’ve upgraded your Windows 10 computer, read on as this post will help you sort out the issue. A lot of users have reported this screen flickering issue in Chrome after having upgraded their devices to a recent Windows 10 build. The bizarre thing about this problem is that it only affects the Google Chrome browser and when it occurs, the Chrome browser will start to flash or flicker. According to users who experience the problem in Chrome, it seems to get worse when they try to play videos on YouTube or other streaming sites. To resolve this problem, many users tried to use Chrome in Incognito Mode, cleared the browser cache as well as cookies. They even tried resetting the browser settings and reinstall Chrome but nothing seems to work. Worry not though as there are still other options you can try to fix the problem and they’re easy ones so you’ll have no problem following them. The screen flickering problem in Chrome appears to be related to the Windows background and color settings as well as incompatible display drivers. This is why it is advised that you have both the video card drivers and Chrome browser updated to prevent the same problem from happening again. To get started troubleshooting the screen flickering issue in Chrome, refer to the following options.

Option 1 – Try modifying the background and colors settings

• Tap the Win + I keys to open the Settings app.
• From Settings, go to Personalization to load the Background Preferences and if this window does not appear, just select the Background option from the left side panel.
• Next, select a Solid Color as the new background from the drop-down menu.
• After that, check if the problem is fixed. This should be fixed especially if the one that’s causing screen flickering is the Windows automatic background switching.
• Once you’ve selected the Solid color as the background preference, go to the Colors tab under Personalization. This will open a new window and from there, check the box of the “Automatically pick an accent color from my background” option.
• Now close the Settings app and open Chrome again.

Option 2 – Try to update or rollback the Graphics driver

You can try to update your Graphics card driver using the Device Manager in your computer to resolve the blank dialog boxes problem or you can also go directly to the website of your graphics card manufacturers like NVIDIA, Intel, or AMD and go to the section called Drivers then check if there’s a new available update – if there is, download and install it. To update your Graphics driver via Device Manager, refer to these steps:

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the Display Adapters and click on them.
• After that, right-click on each entry under the Display Adapters and select the “Uninstall Device” option from the menu.
• Now restart your computer.
• After restarting your computer, go to the Settings app and Check for Updates in the Windows Update section.

Note: If updating the Graphics driver didn’t fix the problem, you can also try to roll back to its previous version and see if that helps.

Option 3 – Try to disable the Hardware Acceleration

For better performance, Google Chrome uses the Hardware Acceleration by default. Unfortunately, there are just some cases when your hardware, GPU to be specific, might not be able to cope with the requirements, resulting in the black screen issue. And if this is your case, you should try to disable the hardware acceleration from your Google Chrome browser settings panel. To do so, follow the steps below.

• Open the Google Chrome settings page.
• Click on the Advanced button to get more options.
• Look for the option called “Use hardware acceleration when available” and then disable it by toggling the button to the left.
• After that, check if the screen flickering issue in Chrome is fixed.

Option 4 – Try to disable “Smooth Scrolling” in Chrome

Disabling “Smooth Scrolling” in Chrome might also help you fix the issue. To do so, follow these steps:

• Open Chrome and type “chrome://flags” and hit Enter.
• Next, look for a flag named “Smooth Scrolling”. You can scroll down until you find it or search it in the Search Flag bar. Note that Smooth Scrolling is enabled by default in the newer versions of Chrome.
• After that, select the drop-down menu and select Disabled.
• Then click on the “Relaunch Now” button.

If you encounter an error saying, “error accessing the registry” when you try to merge a registry key on your Windows 10 computer, you’re not alone as some users also experienced the same problem. According to these users, they encounter the error after they’ve re-installed their Windows version and tried to open a .reg file. Based on the reports, this error could occur if the registry file does not have administrative privileges. Meaning to say, the program does not have the necessary permission to merge the .reg file. This is common with fresh installs as well as reinstalls. Moreover, this kind of issue could also occur due to system file corruption. Whichever the case may be, here are some troubleshooting tips you can check out to resolve the error.

Option 1 – Try to import the .reg file with admin privileges

As pointed out, the error may be due to a lack of admin privileges. It could be that the Registry Editor does not have admin privileges to merge the registry file. This is common with new Windows installations especially since the Registry Editor hasn’t been opened before. So you need to import the .reg file again and this time, with admin privileges.

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and tap the Ctrl + Shift + Enter keys to open the Registry Editor with admin privileges.
• A User Account Control or UAC prompt will appear where you have to click Yes to proceed.
• After opening the Registry Editor, go to File > Import using the ribbon bar at the top.
• Next, use the import menu to go to the location of the file you were trying to merge. Once you’ve found it, click Open to merge it with your current registry. This should fix the problem. If not, refer to the next options below.

Option 2 – Try performing a System Restore

Running System Restore can also help you fix the error when accessing the Registry. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.
• Once the next startup is complete, you have to merge or import the file again and see if the error is now fixed or not.

Option 3 – Try to perform repair install by creating a Windows 10 installation media

• Click this link and then click the Download Tool Now button.
• Next, click the “Use the tool to create installation media (USB flash drive, DVD, or ISO file)…” option and follow the next given instructions on the screen.
• Now select the ISO file option in step 5.
• After that, you should now have an ISO file.
• Next, go to the location where you’ve downloaded the ISO file.
• Then right-click on the Windows 10 ISO file and select the Open with option and then select File Explorer.
• Now click on “setup.exe” and follow the next instructions that appear on the screen. When asked, you have to select either Nothing (clean install) or Keep personal files only option. Take note that you must not select the “Keep personal files, apps, and Windows settings since it doesn’t really work.

Option 4 – Try running the System File Checker Scan

As mentioned, the error when accessing the Registry might be caused by file corruption. And that’s where the SFC scan comes in. The SFC or System File Checker scan could detect and automatically repair damaged system files. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Now restart your computer.

As you know, Windows PowerShell is a useful command-line utility in Windows 10 that can be used to manage the Local Users and Groups which affirms the multiuser operating system principle of Windows 10. Although there are other GUI-based utilities used to manage the Local Users and Groups, there are some system administrators that would still like to use the command-line utility to manage these Local Users and Groups. So in this post, you will be guided on how exactly you can manage the Local Users and Groups using PowerShell on your Windows 10 computer. To get started, refer to the options provided below to manage both the Local Users and Groups using Windows PowerShell.

Option 1 – Manage the Local Users via Windows PowerShell

• You need to first open Windows PowerShell as an admin. To do that, just tap the Win + X keys and select the Windows PowerShell (Admin) option.
• After opening PowerShell, you need to execute the “Get-LocalUser” cmdlet so that you can find all the details about all the local user accounts in your computer which would include the Account Name, Enabled status, as well as description.

Note: On the other hand, you can also get the customized data about several objects that are related to your account. For instance, if you want to check when was the last time the Local account’s password was set, then you need to execute the “Get-LocalUser -Name root | Select-Object PasswordLastSet” cmdlet. Thus, the structure for this cmdlet is “Get-LocalUser -Name root | Select-Object *”. Here are the objects you can use to get different sorts of data:

• AccountExpires
• Description
• Enabled : True
• FullName
• PasswordChangeableDate
• PasswordExpires
• UserMayChangePassword
• PasswordRequired
• PasswordLastSet
• LastLogon
• Name
• SID
• PrincipalSource
• ObjectClass

Option 2 – Manage the Local User Groups using Windows PowerShell

• Like what you did earlier, open Windows PowerShell as admin and then execute the “Get-LocalGroup” cmdlet so you can get all the information about all the groups of all the local user accounts.
• Now if you want to create a new Local User Group, just execute the “New-LocalGroup -Name <NAME OF THE GROUP> -Description '<ENTER THE DESCRIPTION OF THE GROUP HERE>'” cmdlet.
• And if you want to add Local User Accounts to a specific group, just execute the “Add-LocalGroupMember -Group '<NAME OF THE GROUP' -Member ('NAME 1','NAME 2','<ROLE>') -Verbose” cmdlet. You could also use the “Get-Localuser -Name john | Add-LocalGroupMember -Group '<NAME OF THE GROUP>'” cmdlet for the same purpose.
• If you want to display all the User Accounts of a specific group, just use the “Get-LocalGroupMember –Group ‘ ’” cmdlet.
• Now if you want to remove a local user account from a group, all you have to do is use the “Remove-LocalGroupMember -Group '<NAME OF THE GROUP>' –Member <NAME OF THE LOCAL USER ACCOUNT>” cmdlet.

If you suddenly encounter PFN_LIST_CORRUPT Blue Screen of Death error while using your computer then it means that the Page Frame Number or PFN list is corrupted. Page Frame Number is an indexing number used by the hard drive to find out the location of every single file on the physical disk. This kind of Blue Screen error is usually caused by a driver that’s passing a bad memory descriptor list and it can either be temporary or permanent. And so to fix this particular BSOD error, read on as this post contains a couple of suggestions that could help. Keep in mind that when you get a Blue Screen error like PFN_LIST_CORRUPT, the power connection to your PC must not be interrupted and so if you are using a laptop, it’s best if you connect it to a power source. On the other hand, if creating a dump from 0% to 100% takes up more than 5-10 minutes, then you have to force shut down your computer by pressing and holding the Power Key for 10 seconds or at least until the CPU lights turn off. After you do that, proceed to the troubleshooting tips prepared below.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PFN_LIST_CORRUPT. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 2 – Run a System File Checker scan

You can also try to run a System File Checker or SFC scan in order to scan your computer for corrupted files that might be the cause behind the PFN_LIST_CORRUPT error. Once it finds any corrupted system files, it will automatically fix them. To run System File Checker, here’s what you have to do:

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your computer after the scan is completed.

Option 3 – Check for any hard disk errors

• On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
• Next, click on Disk Management on the left side panel.
• From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.

You might also want to run the CHKDSK utility to help you fix any issues with your hard disk. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 4 – Update the Device drivers

Updating the Device drivers can also help you fix the PFN_LIST_CORRUPT Blue Screen error. To do so, follow the steps below.

• Tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. If you see a red or yellow sign that shows up against the driver, right-click on the driver and select “Update Driver Software”.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• Restart your PC and then check if the Blue Screen error is now fixed or not.

Option 5 – Disable OneDrive

The PFN_LIST_CORRUPT error might also be caused by OneDrive. Thus, you have to try disabling this program to resolve the problem.

• Tap the Ctrl + Shift + Esc keys to open the Task Manager.
• Once the Task Manager is open, click on More Details located at the bottom left portion of the window.
• Then go to the Startup tab and select Microsoft OneDrive and then click Disable.

If you are trying to install Office but got an error saying, “Something went wrong, Sorry we ran into a problem” with error codes 12002-4, 12007-4, or 12152-4 instead, this indicates that you have a problem with your internet connection. Aside from internet connection issues, the problem could also be due to some programs that block the installation files to be downloaded so when they time out, you get these error codes. There are several options you can try to fix the 12002-4, 12007-4, or 12152-4 error codes. You can try to install Office offline or turn off the proxy server or VPN (if you’re using one). You can also try to temporarily disable your antivirus program or Firewall. Refer to the given potential fixes below to troubleshoot and fix the problem.

Option 1 – Try to install Office offline

The first thing you can do if you encounter the error codes 12002-4, 12007-4, or 12152-4 when installing Office is to download an offline copy of Office especially when you’re certain that your internet connection is slow. Once you’ve downloaded it, install it again. The offline installer will download both the 32 and 64-bit versions of Office. Keep in mind that you must download the correct version.

Option 2 – Disable the Proxy server

The first thing you can do is to try disabling the Proxy server as it might be the reason why you’re getting error 0x80244022 for Windows Updates. To disable the proxy server, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “inetcpl.cpl” in the field and hit Enter to pull up the Internet Properties.
• After that, go to the Connections tab and select the LAN settings.
• From there. Uncheck the “Use a Proxy Server” option for your LAN and then make sure that the “Automatically detect settings” option is checked.
• Now click the OK and the Apply buttons.
• Restart your PC.

Note: If you are using a third-party proxy service, you have to disable it. In addition, if you are also using a VPN, you can try to disable it as well.

Option 3 – Temporarily disable the Antivirus and Firewall

As mentioned earlier, the downloading of the installation files could be blocked by either the antivirus program or Firewall or it could be both especially when the link seems suspicious. To fix this problem, you have to disable both the antivirus like Windows Defender and the Firewall or any third-party software you might be used temporarily and then download the installation files again. Once the download is completed, make sure to turn on the antivirus program and the Firewall again. On the other hand, you can also try downloading in a different location which also means that you have to try a different network. It could be that the load on the current system is too high which is why it’s not able to offer enough bandwidth to download the installation files of Microsoft Office.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

QuickLook app is one of the best options to preview files without opening them in Windows 10. It works similar to the Quick Look feature of macOS. This Microsoft Store app has some really interesting features. It lets you preview images, documents, and media files. Also, just a hotkey is needed to preview the content of a file. There is no interface for the app. Only a preview window is visible. You can also expand the preview window to full size. Apart from that, it lets you keep the preview window on top of the other opened applications. For image files, it also provides the EXIF data. After installing this app, just select some file that you want to preview, and press the Spacebar key. That’s it! The preview window will open immediately to view the file content. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Hello everyone and welcome to our useful tips and tricks and problem-solving article blog. This time we are doing something different, instead of solving issues this time we are focusing on some quality of life tips like keyboard shortcuts in your Windows 10.

Shortcut Keys	Description
Windows Key	Opens/closes the Start menu.
Windows Key + Up Arrow	Maximizes the selected window.
Windows Key + Down Arrow	Reduces the window size. (Restore down.)
Windows Key + M	Minimizes all open windows.
Windows Key + Shift + M	Opens minimized windows.
Windows Key + Tab	Shows Task View.
Windows Key + L	Locks the screen.
Windows Key + A	Opens the Action Center.
Windows Key + V	Opens Clipboard History.
Windows Key + I	Opens the Settings menu.
Windows Key + F	Opens the Feedback hub.
Windows Key + H	Opens the dictation toolbar.
Windows Key + P	Opens the projection settings.
Windows Key + . (Windows Key + ;)	Opens the emoji panel.
Windows Key + C	Opens Cortana in listening mode.
Windows Key + C (Windows Key + Q)	Opens Windows Search.
Windows Key + G	Opens the Xbox game bar.
Windows Key + X	Opens the secondary start menu.
Windows Key + <number>	Opens the app in the taskbar relative to the number input. For example, if Chrome is the fourth app on the taskbar, using Windows Key + 4 will open Chrome.
Windows Key + Alt + <number>	Opens the right-click menu for the app in the taskbar relative to the number input. For example, if Chrome is the fourth app on the taskbar, using Windows Key + Alt + 4 will open Chrome’s right-click menu.
Windows Key + D	Shows/hides open apps on the desktop.
Windows Key + E	Opens File Explorer.
Windows Key + U	Opens Ease of Access in the Settings menu.
Windows Key + Print Screen	Takes a screenshot of the desktop.
Windows Key + Control + F	Opens the Find Computers window.
Windows Key + Control + D	Creates a virtual desktop.
Windows Key + Control + Left Arrow	Switches to the virtual desktop on the left.
Windows Key + Control + Right Arrow	Switches to the virtual desktop on the right.
Windows Key + Control + F4	Closes the active virtual desktop.
Windows Key + Space	Switches between installed languages (for writing text).

California's Department of Fair Employment & Housing has widened its anti-discrimination lawsuit against Activision Blizzard and claims the publisher has been shredding vital documents relevant to the ongoing investigation. A recent report from Kotaku described the department as offering poorly paid, highly insecure positions, with a culture of hostility towards LGBTQ+ testers. The DFEH's rewording of "employees" to "workers" now hopes to take these contractors' experiences into account. "As a contract employee, I feel there's a lot of pressure to excel, impress, and move through the ranks as fast as you can before your contract ends and you're forced to go 3 months without income or find another job," Axios reports one worker saying. "I take pride in what I do, but it feels like it's never enough." Activision's contentious hiring of union-busting third-party law firm WilmerHale "directly interferes" with its own investigation, it says. By going to WilmerHale, Activision appears to be claiming that all work related to the investigation is privileged and can't be shared with DFEH. The suit also claims that Activision HR shredded documents related to "investigations and complaints", against its legal obligation to retain them during the investigation. The relevant parts of the updated lawsuit were shared by Axios reporters Stephen Totilo and Megan Farokhmanesh, the former also noting that the DFEH "fixed their misspelling of Bill Cosby's name". "DFEH is also informed and aware that documents and records have not been maintained as required by law or by the DFEH's Document Retention Notice," the complaint reads, "including but not limited to documents related to investigations and complaints were shredded by human resource personnel and emails are deleted thirty days after an employees separation."

Speculation and answer from Activision Blizzard

Blizzard employee Jessica Gonzalez suspects that the costs of fines associated with destroying these documents may have been an easier blow for Blizzard to take than any penalties drawn from their existence in helping the lawsuit go through. In an email to Kotaku, Activision denied the shredding allegations and issued a statement outlining steps it had taken to improve company culture—including the ousting of high-level executives like Blizzard president J. Allen Brack. The full statement reads: "Throughout our engagement with the DFEH, we have complied with every proper request in support of its review even as we had been implementing reforms to ensure our workplaces are welcoming and safe for every employee. Those changes continue today, and include:

•     Several high-level personnel changes
•     Revamped hiring and recruiting practices requiring diverse interview panels
•     Greater transparency on pay equity
•     Expanded and improved training and investigative capabilities for human resource and compliance staff
•     Created investigation teams outside of business units to support greater independence
•     Restructured divisions to support greater accountability
•     Enhanced review processes to include evaluation of managers by employees
•     Clear boundaries on workplace behavior with a zero-tolerance approach to harassment and other actions that diminish or marginalize.

"We strive to be a company that recognizes and celebrates the diverse talents and perspectives that lead to the creation of great, globally appealing entertainment. We have provided the DFEH with clear evidence that we do not have gender pay or promotion disparities. Our senior leadership is increasingly diverse, with a growing number of women in key leadership roles across the company. "We share DFEH’s goal of a safe, inclusive workplace that rewards employees equitably and is committed to setting an example that others can follow."

California and RIOT

Beyond Activision Blizzard, California's DFEH has also probed into League of Legends creator Riot Games, accusing the studio of dragging its heels over sexual harassment allegations dating back to 2019. Riot denied the allegations, telling us that it "will never retaliate against anyone for talking to any government agency".

There are times when after you upgrade your Windows operating system, the System Logs under the Event Viewer will display an error message saying, “Event ID 10010 error – The server did not register with DCOM within the required timeout”. What is DCOM? DCOM stands for “Distributed Component Object Model”. It is a proprietary Microsoft technology that allows the Component Object Model or COM software to communicate across a network. You can consider it as an extension of COM which is equipped with the capability of solving a couple of inherent problems related to the COM model to the better use over a network. COM is a tool that’s used for advanced configuration and troubleshooting in Windows 10. Developers usually use it to configure routine components and application behavior like participation in transactions and object pooling and so on. The Component Services needs the DCOM wire protocol in order to communicate with the Component Object Model components on other computers. By default, in a Windows-based system, the network computers are configured initially to enable DCOM. There are also some components in Windows that might require registering themselves with DCOM. However, if they fail to do so, you will encounter the “The server did not register with DCOM within the required timeout” error. To fix this, here are some suggestions you can check out.

Option 1 – Try to use the Component Services

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• Next, double click on the Computers folder located in the right pane and right-click on My Computer, and select the Properties option.
• After that, switch to the COM Security tab under My Computer Properties and then go to the Access Permissions section.
• From there, click the Edit Default button and in the new window that appears, apply the correct permission to objects under the Group or user names section.
• Once you’re done, click OK and exit. This should fix the error.

Option 2 – Make sure that Function Discovery Resource Publication Properties Services is running

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• Next, scroll down and look for the “Function Discovery Resource Publication” entry and double click on it.
• Then switch to the General tab and from there, make sure that the Startup Type is set to “Manual (Triggered).
• You also have to make sure that the service is running so if it’s not, just click on the Start button to start the service.
• Now click on Apply to save the changes made.

Option 3 – Try resetting the default DCOM permissions

• Tap the Win + R keys to open the Run dialog box.
• Then type “dcomcnfg” in the field and tap Enter to pull up Component Services.
• After that, expand Component Services > Computers and right-click on My Computer, and then select Properties.
• Next, go to the Default Properties tab, and in the Default Distributed COM Communication Properties section, make sure that:
  • Default Authentication Level is set to Connect
  • Default Impersonation Level is set to Identify.