New vulnerability found in Windows

If you recently made some changes in your Windows 10 computer using the Group Policy Editor but they were not reflected and you got errors instead, it could be that your Windows computer wasn’t able to read the Group Policy file (registry.pol). To resolve this kind of issue, you have to repair the potentially corrupted Group Policy using the options given in this post. .As you know, Group Policy is a feature in the Microsoft Windows Active Directory which allows an admin to make changes in the features on Windows PCs that are on the network. So if the modifications you just made weren’t successfully applied, then there could be something wrong with the registry.pol file on the client or it could also be that the Group Policy folder is missing. To fix this issue in the Group Policy, you need to refer to the given suggestions below and make sure that you have admin privileges as you execute them.

Option 1 – Try to delete or recreate the missing registry.pol file

The entire settings of the Group Policy are stored in the registry.pol file so if it went missing, all the changes you make will not be reflected. The good thing is that you can recreate it but if the file exists and is corrupted, you need to delete it first before you recreate it.

• First, go to the C:/Windows/System32/GroupPolicy/Machine location.
• And from there, check if the registry.pol file exists or not. If it’s there, just delete it permanently by tapping the Shift + Delete keys.
• Now it’s time to recreate the file. Just open Windows PowerShell with admin privileges by tapping Win + X + A keys.
• After opening PowerShell, type this command: gpupdate /force
• The command you entered will recreate the registry.pol file and will refresh the Group Policy. Restart your computer.

Option 2 – Try recreating the secedit.sdb file

The security settings of Group Policy are stored in the secedit.sdb file so if you made some changes to security and they weren’t reflected, you can try to delete and recreate the secedit.sdb file instead of deleting the Group Policy file. All you have to do is navigate to the C:/WINDOWS/security/Database folder and look for the secedit.sdb file and rename it or move it to another folder. After that, restart your computer. Once your computer has restarted, the secedit.sdb file will be created again.

Option 3 – Try to reset the Group Policy to default

You can also try to reset the Group Policy back to its default state. There are several ways you can do that. You can either use the gpupdate or the secedit command in the Windows PowerShell to do that. Resetting the Group Policy will resolve any issues that could be caused by its current settings.

Option 4 – Try to perform System Restore

System Restore can also help resolve the Group Policy issue. It could be that prior to the issue, you’ve made some changes in the system that might have affected the Group Policy. To undo these changes, perform System Restore.

• First, 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.

Option 5 – Use the DISM tool

You can also try running the Deployment Imaging and Servicing Management or DISM tool. This tool will repair the Windows System Image as well as the Windows Component Store in your Windows 10 computer. So if there are any missing or corrupted folders and files, the DISM tool can restore and repair them. As a result, any system consistencies and corruptions will be fixed. To run this tool, follow these steps:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer.

The printer can stop working for many various reasons, some of them are however tied to the printer driver itself. In this guide, we will address issues and provide you with advice on how to get your printer back in working order in no time. All of that being said let us fix your Printer driver issue.

1. Check to see if the printer is plugged and that it has toner or colors and paper in the tray

   The simplest solutions are the best ones, and most of the time simplest issues are overlooked. To eliminate any basic issues check the printer cable does it has paper in the tray and check the status of toner or colors in it.

2. Check if Windows troubleshooter will resolve the issue

   Bring up settings and choose devices, under devices click on printers and scanners. On the far right top, you have a link to start the troubleshooter, click on it. Windows built-in tools could resolve issues and fix them for you. If by any chance Windows is not able to find or resolve issues move to the next step.

3. Check if the Device Manager is reporting an error and update the driver

   If the hardware is functioning properly then the issue might be in Windows not detecting device or driver malfunction. In any case, the Device Manager will be the one who will report this problem. In order to check to see if the driver is properly working press ⊞ WINDOWS + X to open the hidden start menu. Once it opens, click on Device Manager to open it, If you have a driver device error inside Windows, you should see it immediately when entering the Device Manager, it will have a yellow exclamation mark beside it. Right-click on it and choose update driver.

4. Reinstall driver

   If driver update failed or you already have the latest drivers, reinstalling them could fix the issue since drivers might have corrupted during installation of some update or application. Follow steps from point 3 to get to the driver in Device Manager, then right-click on it but instead of update choose to uninstall. Reboot Windows once the driver is uninstalled and Windows will install a new one automatically. If you do not want to update drivers automatically install the latest driver for your device, then reboot.

5. Check Windows update

   Check to see if the latest Windows update is installed, update your Windows if needed

6. Fix driver issue with DRIVERFIX

   If everything else fails, get DRIVERFIX, a premium solution for your PC issues, and fix driver errors.

If you encounter Windows Update error 0x80092004 while trying to update your Windows 10 computer, then this post is for you. This kind of Windows Update error could be due to many reasons but none of them includes your hardware or installed driver software. Microsoft releases updates that are either not supposed to go out, or you install them when you click on the Check for Update button which can install updates that have not finished testing yet. As a result, you may encounter the Windows Update error 0x80092004 To resolve the Windows Update error 0x80092004, here are some fixes you can try.

Option 1 – Try removing recent updates and packages

When a Windows Update fails, it mostly rolls back and cleans up all its residues. However, there are times when it doesn’t and you can clean that package manually. To remove recent updates and packages, you can go to the Update History and find out what KB updates were installed and once you’ve figured it out, you can execute the DISM tool to remove it manually.

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, execute the “Dism /online /Get-Packages”. This will give you a list of packages that were recently installed.
• Now run the Remove Package program to remove the concerned update and package.

dism.exe /online /remove-package /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.248.1.17 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6 /packagename:Package_for_RollupFix_Wrapper~31bf3856ad364e35~amd64~~16299.192.1.9 /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9 /norestart

• Now restart your computer and log back in.
• After that, run the following command:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

• Then scan for updates.

Note: Keep in mind that the remove package command is made for AMD 64-bit machines specifically.

Option 2 – Try deleting the files from the SoftwareDistribution folder and resetting the Catroot2 folder

The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the “We couldn’t install some updates because the PC was turned off” error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try to manually install the Windows Updates

Windows Update Error 0x80092004 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

If you were trying to update your Windows 10 computer and failed due to Error Code 0x80240438, then you’ve come to the right place as this post will give you a couple of suggestions you can check out to resolve this error. You can encounter Error Code 0x80240438 not just in Windows Updates but also in Microsoft Store. This is due to the fact that the delivery mechanism for both Windows Updates and Microsoft Store is common and interdependent. This is why a lot of Windows Update and Microsoft Store error codes are similar. And so fixing them won’t be that hard as well since most methods are basically the same. When you encounter this kind of error in Windows Update or Microsoft Store, you will see the following error message on your screen:

“There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help – (0x80240438).”

To resolve Error Code 0x80240438, here are some potential fixes you need to check out:

Option 1 – Try to run the Windows Update Troubleshooter

The Windows 10 Store Apps Troubleshooter will help you in fixing the Error Code 0x80240438. This is a great built-in tool from Microsoft that helps users fix any app installation issues. So this is worth a try to solve the problem. This built-in tool also helps you fix the Windows 10 Store if it isn’t working. To use the Windows Store Troubleshooter, follow the steps below.

• Tap Win + I keys again to open the Windows Settings panel.
• Go to Update & Security and then go to Troubleshoot.
• Under the Troubleshoot section, on your left-hand side, scroll down to find Windows Update and then click on Run the troubleshooter option and follow the on-screen instructions and then see if it fixes the problem.

Option 2 – Try to temporarily disable anti-virus and Windows Defender Firewall

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like Error Code 0x80240438 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program and Windows Defender Firewall for the meantime and check if it fixes the error or not.

Option 3 – Disable the Proxy server

You can also try to disable the Proxy server for your LAN to fix Error Code 0x80240438 especially if your computer was attacked by some malware or adware recently. In such cases, there is a chance that the malware or adware has changed your network settings in order to generate intrusive advertisements. Thus, you have to disable the proxy server and you can do that by following these steps:

• 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.

Option 4 – Try modifying the “Remove access to use all the Windows Update features” Policy

• Start by tapping the Win + R key combination to open the Run utility.
• Then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Once you’ve pulled up the Group Policy Editor, navigate to this setting: User Configuration > Administrative Templates > Windows Components > Windows Update
• Next, double click on the “Remove access to use all the Windows Update features” policy and set its radio button to “Not Configured”. As you can see, this policy setting has the following description:

“This setting allows you to remove access to Windows Update. If you enable this setting, all Windows Update features are removed. This includes blocking access to the Windows Update Web site at http://windowsupdate.microsoft.com, from the Windows Update hyperlink on the Start menu, and also on the Tools menu in Internet Explorer. Windows automatic updating is also disabled; you will neither be notified about nor will you receive critical updates from Windows Update. This setting also prevents Device Manager from automatically installing driver updates from the Windows Update Web site.”

If you enable this policy setting, you can configure one of the following notification options:

• 0 = Do not show any notifications: This setting will remove all access to Windows Update features, and no notifications will be shown.
• 1 = Show restart required notifications – This setting will show notifications about restarts that are required to complete an installation.
• Now you need to exit the Group Policy Editor and restart your computer for the changes to take effect.

Option 5 – Try resetting the Windows Update folders

Resetting the Windows Update folders can also help in fixing the error in both Windows Update and Microsoft Store. All you have to do is delete the contents in both the SoftwareDistribution folder and reset the Catroot2 folder as well.

Option 6 – Try downloading and installing the Windows Updates manually

Error Code 0x80240438 might be due to a Windows Update that has failed. So if it is not a feature update and only a cumulative update, you can download the Windows Update and install it manually. But first, you need to find out which update has failed, and to do so, refer to the following steps:

• Go to Settings and from there go to Update and Security > View Update History.
• Next, check which particular update has failed. Note that Updates that have failed to install will be displayed under the Status column which has a label of “Failed”.
• After that, go to the Microsoft Download Center and look for that update using its KB number and once you find it, download and then install it manually.

Note: You can also use the Microsoft Update Catalog, a service from Microsoft that provides a list of software updates that can be distributed over a corporate network. With the help of this service, it can be easier for you to find Microsoft software updates, drivers as well as fixes.

If you were trying to print some documents but encounter the HIDCLASS.SYS Blue Screen error instead, then you’ve come to the right place as this post will guide you in fixing any Blue Screen errors related to the HIDCLASS.SYS file. HIDCLASS.SYS is a Windows operating system driver file. HID or Human Interface Device includes Keyboards, mice, and other input devices. HIDCLASS.SYS is a critical system driver file that is responsible for connecting different kinds of devices all over the system, including the functionality where a Word Processor can access the printer to print documents. This file comes under the category of kernel-mode device drivers and if the driver fails, it can result in a Stop Error. There are a lot of Stop errors related to the HIDCLASS.SYS file, such as:

• KMODE EXCEPTION NOT HANDLED
• SYSTEM SERVICE EXCEPTION
• DRIVER POWER STATE FAILURE
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• DRIVER VERIFIER IOMANAGER VIOLATION
• IRQL NOT LESS EQUAL

The fixes for the Blue Screen errors related to the HIDCLASS.SYS files are pretty simple but before you troubleshoot the problem using these fixes, make sure that you boot your computer into Safe Mode with Networking first. After that, get started on these tips:

Option 1 – Update or rollback or disable concerned device drivers

To fix the HIDCLASS.SYS error, you can also try to roll back, or update, or disable the concerned device drivers.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers particularly the ones that are under the sections of Keyboard, Mouse, USB, and HID Drivers.
• Next, right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions or disable them.

Option 2 – Check for any incompatible devices

The next thing you can do to troubleshoot the HIDCLASS.SYS Stop error is to plug in and out each one of the different hardware that is connected to your computer. Doing so will help you determine which one of the hardware is the one that’s triggering the error to pop up. You will also know what hardware drivers or anything else that could be causing this error which includes external devices like mouse, keyboard, printer, as well as internally attached components like the Graphics card and so on.

Option 3 – Try running the ChkDsk utility

Running the ChkDsk utility can also help you resolve any Blue Screen errors related to the HIDCLASS.SYS file. To run this tool, refer to these steps:

• First, open This PC and right-click on your operating system partition for Windows.
• Next, click on Properties and navigate to the Tools tab.
• Then click on Check under the Error Checking section.
• After that, a new mini window will be opened and from there click on Scan drive and let it scan your disk drive partition for any errors and then restart your computer.

Option 4 – Try checking the Memory for any errors

• Tap the Win + R keys to open Run and type exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them.

Option 5 – Run the System File Checker

System File Checker or 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.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• 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 and see if the Blue Screen error is fixed or not.

If you open any program in your Windows 10 PC such as Outlook and suddenly get an error message saying, “Failed to register a VB Script dll. Reinstall or run Regsvr32.exe Vbscript.dll to self-register”, read on, as this post will guide you on what you can do to fix it. The obvious solution to this problem is by re-registering the “vbscript.dll” file on your computer. Refer to the instructions given below to re-register the VB Script DLL file and to fix the error.

• Step 1: Open the Command Prompt as an administrator from the WinX Menu.
• Step 2: After opening Command Prompt, type in the following command and tap Enter on your keyboard.

regsvr32.exe vbscript.dll

• Step 3: Once you enter the command, it will re-register the VB Script DLL file using the Windows OS tool called Regsvr32 or regsvr32.exe. This tool is a command-line utility used to register and unregister OLE controls such as DLL and ActiveX (OCX) controls in the Windows environment. After the execution of the command, you should see the following pop-up on your screen which means the re-registering of the concerned DLL file has succeeded.

On the other hand, if re-registering the DLL file didn’t work, then you can try logging in using an administrator account and then register the DLL file again or you could also use the System File Checker to figure out what the problem really is and automatically fix it. System File Checker or 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.

Minecraft has taken the world by the storm, it was an indie project game and it went mainstream. Dream of every game developer I guess. The dream of every gamer on the other hand is to double click on the game and to play it and not to deal with various issues, especially if they are launch issues. Luckily for all of you gamers, here at errortools we game as well and we are happy to bring you a solution on how to fix Minecraft won't launch issue. So sit back, relax and keep on reading, and hopefully enough you will be gaming again in no time. Follow the guide presented step by step, point by point how it is presented for the quickest way to get back in Minecraft. This guide also presumes that your hardware configurations meet at least the minimum system requirements for running Minecraft.

1. Disable antivirus and firewall

   90% of the time this is the issue why Minecraft is not working, your antivirus or firewall has detected it as a false positive, and access to system internet, etc has been cut. Try disabling it and if everything is working fine add it to the antivirus or the firewall exception list.

2. Run Minecraft as admin

   Minecraft will sometimes refuse to run if it does not has administrator privileges. To make sure this is the case locate the Minecraft executable, right-click on it and choose properties. Go to the compatibility tab and check Run as Administrator box.

3. End Minecraft process

   It came to knowledge that even if Minecraft is not running it can have its processes active in the background. Press CTRL + SHIFT + ESC to open task manager Locate if Minecraft has a process running If you find the Minecraft process right-click on it and choose End Task

4. Run Minecraft in compatibility mode

   If Minecraft still refuses to start try running it in compatibility mode in the previous Windows version Locate Minecraft executable file in its install location Right-click on it and choose properties In the properties, windows go to the compatibility tab Check run this program in compatibility mode for: Select previous version of the operating system, try Windows 8 or Windows 7

5. Update graphic card driver

   The best bet is to go to your GPU manufacturer's website and download the latest version of the driver of your GPU.

6. Remove mods, plugins, texture packs

   Mods, plugins, texture packs are all great but sometimes they can cause GPU overloads and other issues to see if this is the case try running Minecraft in Vannila mode without anything installed, just pure and clean Minecraft as it was just downloaded and installed.

7. Reinstall Minecraft

   If everything else failed, reinstall Minecraft. There might be a chance that some DLL file was deleted or corrupted by mistake or that some crucial files are missing. Clean reinstallation will fix all of these issues.

What is BitCoinMiner Malware?

BitCoinMiner is a Malware created with the intent to force computer systems to generate crypto-currency, namely Bitcoin. This is done without the consent and knowledge of a computer/system holder. This unwanted file bears no digital signature or publisher since the creators of such a heinous invention do not wish to be known. Technical details about BitCoinMiner Malware include:

Product Version: 1.0.0.0 Original File Name: crss.exe Entry Point:  0x000C5AAE

Assessment of BitCoinMiner Malware

After installation of the BitCoinMiner Malware, there were no visible signs of an infection or program files installed. However, based on research, BitcoinMiner Malware utilizes the CPU’s resources (est. to be about 50%). Computer users have reported that they recognized an unknown process utilizing the majority of their processing space. the bitcoin miner is used by the creators to penetrate a user’s system, in effect coercing each infected system to mine Bitcoins covertly. After years of mining, a user might discern that their computer is moving slouchy and may even encounter various forms of BSODs.   After Bitcoins have been mined in the infiltrated system, the cyber currency is then returned/ sent to the creator of the malware. This venture is a sly and deceptive way to earn Bitcoins since the currency is gaining much popularity.

Further Information on BitCoinMiner

BitCoinMiner works covertly. There are no obvious traces of this program running on a computer system. However, once a computer system is infiltrated, the computer user will realize that their CPU resources are strangely being used up, even while the computer idles. Another expression of BitCoinMiner is the addition of cookies of various sorts to a computer system. These include:

• Tracking cookies
• Advert (Adware) cookies
• Casale Media (Spyware) cookies
• Atwola (Spyware) cookies
• Adtech (Spyware) cookies

Once BitCoinMiner is present on a computer system, it can potentially slow it down and also create back doors as a means to install other unwanted and harmful programs. To completely remove BitCoinMiner Malware from your computer, click here to download and install Spyhunter.

Following a two-year investigation by the California Department of Fair Employment and Housing, the state has filed a lawsuit against Activision Blizzard for fostering a "frat boy" culture in which female employees are allegedly subjected to unequal pay and sexual harassment. As reported by Bloomberg, Activision Blizzard is being accused by the state of California of discriminating against female employees at nearly all levels of employment, including in regards to compensation, promotion, assignments, and termination. The state alleges Activision Blizzard’s leadership has failed to address any of these outstanding issues or prevent them from occurring within the workplace. You can read the full details of the lawsuit here. The suit, filed Tuesday in the Los Angeles Superior Court, says Activision Blizzard, which is made up of about 20 percent women, assigns women, and women of color, to "lower paid and lower opportunity levels" with lower starting pay for similar work as their male counterparts. The documents also accuse Activision Blizzard of fostering a "pervasive 'frat boy' workplace culture in the office. Male employees are said to drink "copious amounts of alcohol" as they make their way through cubicles and "often engage in inappropriate behavior toward female employees." Male employees are said to come to work hungover, play video games during work "while delegating their responsibilities to female employees, engage in banter about their sexual encounters, talk openly about female bodies, and joke about rape." The lawsuit also cites one particular incident where a female employee, who was already subjected to intense sexual harassment at the company, committed suicide during a work trip with a male supervisor who allegedly brought inappropriate, sexual items with him on the trip. The lawsuit is asking for an injunction that will force Activision Blizzard to comply with workplace protections, as well as deliver unpaid wages, pay adjustments, back pay, and lost wages and benefits for female employees.

An Activision Blizzard spokesperson sent the following statement in response to the allegations:

We value diversity and strive to foster a workplace that offers inclusivity for everyone. There is no place in our company or industry, or any industry, for sexual misconduct or harassment of any kind. We take every allegation seriously and investigate all claims. In cases related to misconduct, the action was taken to address the issue. The DFEH includes distorted, and in many cases false, descriptions of Blizzard’s past. We have been extremely cooperative with the DFEH throughout their investigation, including providing them with extensive data and ample documentation, but they refused to inform us what issues they perceived. They were required by law to adequately investigate and to have good faith discussions with us to better understand and to resolve any claims or concerns before going to litigation, but they failed to do so. Instead, they rushed to file an inaccurate complaint, as we will demonstrate in court. We are sickened by the reprehensible conduct of the DFEH to drag into the complaint the tragic suicide of an employee whose passing has no bearing whatsoever on this case and with no regard for her grieving family. While we find this behavior to be disgraceful and unprofessional, it is, unfortunately, an example of how they have conducted themselves throughout the course of their investigation. It is this type of irresponsible behavior from unaccountable State bureaucrats that are driving many of the State’s best businesses out of California. The picture the DFEH paints is not the Blizzard workplace of today. Over the past several years and continuing since the initial investigation started, we’ve made significant changes to address company culture and reflect more diversity within our leadership teams. We’ve updated our Code of Conduct to emphasize a strict non-retaliation focus, amplified internal programs and channels for employees to report violations, including the “ASK List” with a confidential integrity hotline, and introduced an Employee Relations team dedicated to investigating employee concerns. We have strengthened our commitment to diversity, equity, and inclusion and combined our Employee Networks at a global level, to provide additional support. Employees must also undergo regular anti-harassment training and have done so for many years. We put tremendous effort into creating fair and rewarding compensation packages and policies that reflect our culture and business, and we strive to pay all employees fairly for equal or substantially similar work. We take a variety of proactive steps to ensure that pay is driven by non-discriminatory factors. For example, we reward and compensate employees based on their performance, and we conduct extensive anti-discrimination training including for those who are part of the compensation process. We are confident in our ability to demonstrate our practices as an equal opportunity employer that fosters a supportive, diverse, and inclusive workplace for our people, and we are committed to continuing this effort in the years to come. It is a shame that the DFEH did not want to engage with us on what they thought they were seeing in their investigation.

Conclusion

We will see how things work out, but I am not too optimistic for Activision Blizzard, truth to be told these reports are really bringing up some disturbing news on the sunlight. I just hope that all responsible will be brought to justice.

Recently, some users reported not being able to boot up their Windows 10 computers. And during the startup phase, at some time, the bootup sequence is halted with a Recovery error along with an error message saying, “Your PC/Device needs to be repaired” with an error code of 0x0000605. This kind of error message indicates that Windows was not able to verify the digital signature for the file as the signing certificate or it could be that it has expired. To resolve this error, you can follow the potential fixes given below and see if you stumble upon a fix that might work out for you.

Option 1 – Change the Date & Time settings in the BIOS

Some users reported that they were able to fix the error by changing the Date & Time settings in the BIOS. Upon checking, they saw that in their BIOS settings, the date was off several years. As a result, the incorrect date and time settings end up ticking the system into believing that the Windows build has expired long before the actual expiration date. You can check if the error pops up due to the same reasons by accessing the BIOS settings. To do so, you have to tap the Boot key that’s associated with your motherboard manufacturer during the initial startup phase. After that, you can search for a particular boot key online or you can also tap keys like F2, F4, F8, F10, F12, and the Delete key. Once you’re able to access the BIOS settings, locate the Date & time or anything similar, and then check if the date is correct or not. If not, you need to change the date to the actual date and then save the changes made and restart your computer and then check if the issue is now fixed or not. Just remember that if the actual date is past the expiration date of the build you have, you need to change it to an older date. If your Windows 10 PC is able to boot back up, you have to update it to a stable Windows build and then go back to the BIOS settings and change the date to the current one else you will definitely encounter Windows update errors in the future as well as security alerts.

Option 2 – Perform a clean install of a stable Windows 10 build

If every system boot fails accompanied by a BSOD error with error code 0x0000605 “A component of the operating system has expired” and you’ve already followed every instruction on option 1, then it’s most likely that your current Windows build has already expired. Remember that almost all the Windows 10 Insider Preview builds (98xx) are created along with an expiration date and when your computer reaches the expiration date, you won’t be able to boot your computer up. Note that the exact expiration date varies based on the build number. And prior to the expiration date, the operating system will start to display some error warnings telling you that the build will expire and urge you to update the most recent build available. And so once the computer reaches its expiration date, it will begin to reboot every three hours until it no longer boots up which is about 2 weeks approximately after the license has expired. Once the expiration date is up and your computer no longer boots up, you need to perform a clean install and then install the latest Windows 10 build to resolve the issue once and for all.