How to remove Nectar Toolbar from your Windows PC

Browsing your files on a computer seamlessly is made possible by the File Explorer in Windows 10 as it provides users with a great sense of customization for both listing and performing operations on a file. You have the option to arrange the folders and files being browsed by their name, type, date, size, and so on. Moreover, files that share a common attribute can be also be grouped accordingly using the grouping feature. However, there are times when instead of helping, it causes some problems for some users. This is why in this post, you will be guided on how you can disable the File Grouping feature in the File Explorer in Windows 10. There are two methods you need to consider in disabling the File Grouping feature in Windows 10. First, you can disable it for only one folder or you can disable it for all the folders on your computer. For more details, follow the instructions given below.

Option 1 – Disable File Grouping in only one folder

This first option is relatively straightforward and simple which will work if you only want to disable File Grouping in one folder.

• First, open File Explorer, and go to the folder you want to disable File Grouping.
• Next, right-click anywhere on that folder.
• And then select Group by > None. This will disable File Grouping for only that particular folder.

Option 2 – Disable File Grouping in all the folders

If you wish to disable File Grouping in all the folders on your computer, then you need to follow this option. If you have already tried the first one, then continue with the given steps below.

• Tap the Alt + V key combination.
• Then tap the Alt + Y keys and then tap Alt + O keys.
• After that, navigate to the View tab, and under the Folder views section, select Apply to Folders.
• Now click on the Apply and OK buttons to save the changes made. This will disable File Grouping in all the folders listed in the File Explorer.

If you encounter errors 1603 and 0x00000643 on your Windows 10 computer while trying to install or update your Google Chrome browser. Although most errors can be fixed by some simple troubleshooting steps, that is not the case for these two errors since they have pretty specific solutions. To resolve errors 1603 and 0x00000643 on your Chrome browser, here are some solutions you need to check out.

Option 1 – Try to run Microsoft Install and Uninstall Troubleshooter

Running the Microsoft Install and Uninstall Troubleshooter could help you fix errors 1603 and 0x00000643 in Chrome as well as the following issue in your Windows 10 computer:

• Corrupted registry keys on 64-bit operating systems.
• Corrupted registry keys that control the updated data.
• Problems that:
  • Prevent new programs from being installed.
  • Prevent new programs from being installed.
  • Problems that block you from uninstalling a program through Add or Remove Programs (or Programs and Features) in Control Panel.

To use the Microsoft Install and Uninstall Troubleshooter, refer to the given steps below.

• First, right-click on the downloaded MicrosoftProgram_Install_and_Uninstall.meta.diagcab file and run it with administrative privileges.
• Next, it will offer you two scenarios to troubleshoot namely, “Installing” or “Uninstalling” and you have to select Installing to resolve the current errors.
• After that, it will show you a list of available programs on your computer. From there, select Google Update Helper and then click Next.
• It will then start to troubleshoot the problem and will automatically apply the fixes for you. It will offer you to uninstall Chrome if it turns out that it’s the root cause of the problem.
• After that, you need to download Google Chrome again and then reinstall it.

Option 2 – Try to clean reinstall Chrome

There are instances when programs leave files behind after you’ve uninstalled them and the same thing can happen to Chrome so before you reinstall Chrome, you have to make sure that you have deleted the User Data folder. To do so, refer to the following steps:

• Hit the Win + R keys to open the Run dialog box.
• Next, type “%LOCALAPPDATA%GoogleChromeUser Data” in the field and hit Enter to open the User Data folder.
• From there, rename the default folder and name it something else, e.g. “Default.old”.
• After that, install Google Chrome again and check if the issue is now fixed.

Option 3 – Try running the Chrome Cleanup tool

You might want to run Google Chrome’s built-in Malware Scanner & Cleanup tool as it could also help in getting rid of any unwanted ads, pop-ups, and even malware, as well as unusual startup pages, toolbars, and anything else that might overtake the network and could affect the performance of the browser.

Option 4 – Try to run the Network Troubleshooter

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

Option 5 – Reset Chrome

Resetting Chrome can also help you fix the error. This means that you will be restoring its default settings, disabling all the extensions, add-ons, and themes. Aside from that, the content settings will be reset as well and the cookies, cache, and site data will also be deleted. To reset Chrome, here’s what you have to do:

• Open Google Chrome, then tap the Alt + F keys.
• After that, click on Settings.
• Next, scroll down until you see the Advanced option, once you see it, click on it.
• After clicking the Advanced option, go to the “Restore and clean up option and click on the “Restore settings to their original defaults” option to reset Google Chrome.
• Now restart Google Chrome.

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.

When you encounter an error message that says, Chassis Intruded…Fatal Error…System Halted on your monitor then it indicates that the Chassis or the cabinet that holds the CPU, GPU, motherboard, and many more is open. It is a security feature offered by OEMs wherein a connector that is found in the motherboard can detect if the chassis component has been replaced or removed. There are a few OEMs that offer onboard speaker or PC chassis speaker which goes off in this kind of situation. Obviously, the problem has something to do with the hardware and in most cases, you have to put the jumper back on the motherboard with the pin-labeled chassis signal and ground. There are times when some OEMs offer a simple switch that is armed automatically when you properly close the chassis. Thus, you need to check if this switch has something to do with the error. If there is no switch or if it doesn’t resolve the issue, although you may be able to get into Windows with a warm boot, the normal Windows boot won’t really work unless you fix the problem. It is rather false positive and has something to do with the RTC RAM state or the BIOS. You might need to completely disable the Chassis intrusion feature to fix the error. Refer to the suggestions given below to try and fix the “Chassis Intruded, Fatal Error … System Halted” error.

Option 1 – Try to clear CMOS

You can easily clear CMOS by shorting two pins which can be found side by side on the motherboard. Keep in mind that it may vary from OEM to OEM although the basics are still the same to clear CMOS. In addition, you might also have to download the manual from the OEM’s website so that you’ll know its exact location.

Option 2 – Try booting into the BIOS

You can also try booting into the BIOS. All you have to do is tap either the DEL or F2 keys to get there. Note that everything will be set back to their default setting after you reset the CMOS.

Option 3 – Try disabling Chassis intrusion

In this option, you have to look for the Chassis intrusion feature in your BIOS. It might be located under security. From there, disable it and check if the problem’s fixed.

Option 4 – Try to reconfigure the BIOS

Once you have disabled the Chassis feature, you need to reconfigure the BIOS the way you expect it to be or to what it was before the reset.

Recently, a number of users reported an error while trying to update their computers. This particular Windows Update error has an error code of 0x80073701. If you are one of the users who encounter this error, then read on as this post will guide you on how exactly you can fix it. Here’s the exact context of the error:

“Updates failed. There were problems installing some updates, but we’ll try again later. 2019-07 Cumulative Update for Windows 10 Version 1903 for x86-based Systems (KB4507453) – Error 0x80073701”

The Windows Update Error 0x80073701 also comes with a code “ERROR_SXS_ASSEMBLY_MISSING” which indicates that some system files are missing on your computer that caused the update installation failure error. Although this Windows Update error does not cause any severe issues, it is still being reported in the section of Windows Update where it is marked as “Update failed”. There are several potential solutions you can check out to resolve this error. You can try to run the DISM tool or the SFC or System File Checker scan. You could also try to run the Windows Update troubleshooter. For more information, make sure to follow the options given below.

Option 1 – Restart your computer and try installing the Updates again

Restarting your computer can also help in fixing the Windows Update failed to install error 0x80073701. There are cases where the issue resolves on its own as it could just be some simple network or PC error.

Option 2 – Try to run the DISM tool

Running the DISM Tool helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt as admin.
• Then type in this command: exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

After you run this tool, a log file is created at C:WindowsLogsCBSCBS.log. On the other hand, if the Windows Update client is already broken, you will be prompted to use a running Windows installation as the repair source or use a Windows side-by-side folder from a network share, as the source of the files. Although the chances of this happening is less, if it turns out to be the case, you need to run an advanced command in the DISM tool to repair a broken Windows Update. Just repeat the process above but use the following command instead:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Option 3 – Try to 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 to good system files that might be causing the error 0x80073701. 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.

• Restart your computer.

Option 4 – Try running the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80073701. 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.

It really sucks when you can’t fully enjoy the newest version of your favorite OS.

Windows 11 is still relatively fresh and consequently has some annoying little bugs that really ruin our experience. The good news is that you’re not alone and most of them are easy to fix.

Here are 5 commonly reported Windows 11 issues and what you can do to get rid of them.

1. Windows 11 audio problems

One of the absolute most irritating things in the world is struggling with the sound on your computer. Windows 11 users have reported facing the issue of low or no sound. If you’re currently experiencing the same frustration, you can be relieved. Chances are fixing it will only take a few minutes.

The first thing to check would be whether you accidentally muted your device by pressing the mute button on your keyboard. Yes, we know it sounds a lot like the old “have you tried turning it off and on again?” But it’s important to leave no stone unturned, and the most obvious things are usually the ones we easily overlook.

Moreover, if you have several audio output sources, check whether the right one is selected. You can do this via the Action Center or through Settings. If you want to use the same source every time, we also recommend you set it as the default one.

It’s also important to have a good, up-to-date audio driver. More often than not, this will be the true cause of your audio struggles. Make sure to update your driver, and if that doesn’t work out, you can always un- and reinstall it or install a different one. 

Lastly, if all attempts remain unsuccessful, run the audio troubleshooter to figure out what’s actually going wrong.

2. Unable to find files

Such a powerful new operating system, yet it can’t seem to do the simplest thing imaginable? The File Explorer not responding on Windows 11 is one of the most frustrating and most common problems with Microsoft’s newest iteration of its awesome OS.

However, 9/10 times it can be fixed by simply restarting your PC. You could also try killing the Windows Explorer process in the Task Manager and then rerunning it.

If these don’t help, check whether there are any pending Windows 11 updates. A single missing update can compromise your PC’s functionality, so always make sure to install them all on time. 

Should none of that work, then there are other ways to solve the File Explorer problem. However, then the issue is probably a bit deeper and it’s no longer in the ‘easy fix’ territory.

3. Start menu not working

Just like the File Explorer, the Start menu is a fundamental element of your OS. So, it’s only natural that its malfunction grinds your gears. It may be more customizable than on previous Windows versions, but it doesn’t always work smoothly. 

If you’re facing the so-called Start menu critical error, there are a few things this could be caused by. Usually it means you turned off your system while an important update was still being installed, there is a corrupt file on your PC, or Windows forcefully stopped a program. 

Whatever the reason, the solution should be pretty simple. Try the basic steps: restarting your File Explorer (like we explained above) and signing out and back into your account. If that doesn’t do anything, you may want to try uninstalling third-party start menu apps (if you have any), since they can interfere with your default programs’ functionality.

Now, those are the easy fixes. If you get nowhere with them, you might need to identify the root cause and search for more complex solutions than that.

4. Snipping tool not working

Our beloved screenshot tool was introduced with Windows 10 and Microsoft decided to keep it. However, you were probably just as disappointed as us when you tried to run it and failed. 

Normally, this can be fixed by installing the latest Out-of-band (OOB) update, or even pending updates in general. Even if your system appears to be up-to-date, run the checker just in case.

Another cool thing Windows 11 lets you do is ‘Repair’ and ‘Reset’, which is the easiest way to troubleshoot your Snipping tool. If this fails, you can also try the good old un- and reinstall method. Simply uninstall the tool through the Control Panel and reinstall it from the Microsoft Store.

Furthermore, in the case of an upgrade from Windows 10 to 11, it may be that the old Snipping tool version is interfering with the launch of the new one. If you don’t care that much about the additional options available with the enhanced screenshot tool, you can use the old version instead.

Simply go to your C Drive, find the Windows.old folder, search for the tool and open it from there. Make sure to pin it to your taskbar as well, if you know you’re going to use it often.

5. Can’t install the latest update

The latest Windows 11 version, 22H2, has brought tons of enhancements to our dearest operating system. Unfortunately, a lot of users still haven’t had the opportunity to experience it. A mere update of your OS version should be the one thing that goes smoothly, but sometimes that’s not the case.

Failure to install 22H2 can be caused by a few things. Most commonly, the issue is caused by lack of storage space or corrupted files, but there could be other culprits.

There are a couple of things you could try. For example, it’s crucial that your drivers be up-to-date and some important services be enabled. These are: Windows Modules Installer, Background Intelligent Transfer Service, Cryptographic Service, Windows Update services.

To enable them, search ‘Services’, find the service you need and right-click on it. Open ‘Properties’ and select the startup type ‘Automatic’.

It may also be necessary to unplug all peripherals that aren’t crucial and disable third-party antivirus tools until after the update is finished. 

Ultimately, you can run the Windows Update troubleshooter to detect and fix other possible issues.

Summary

Tiny bugs like these are nothing out of the ordinary. That said, we still all hate when they happen.

Hopefully some of our solutions have helped you to a smoother Windows 11 experience. But if you’re still struggling, feel free to reach out to us. We’d be happy to help!

JavaScript Void 0 Error - What is it?

JavaScript is a computer programming language used to make a website work smoothly with the internet. It helps to display visual effects, animations, and other web page functions. You may come across the JavaScript Void (0) error message when there is a problem in loading JavaScript from a web page or the internet browser.

Error Causes

JavaScript Void (0) error is triggered by multiple reasons such as:

• It can be due to a simple random Windows application glitch.
• You are visiting an unsafe website that contains malware
• JavaScript’s web browser implementation  is broken due to poor program installation
• Active X controls, Java applets, and active scripting, the key components of JavaScript are disabled
• Registry issues like invalid or misconfigured registry keys

Further Information and Manual Repair

For JavaScript Void (0) error-free web surfing, it is advisable to repair the issue without any delays. Let’s take a look at different methods to resolve this error on your system.

Cause: Simple Random Glitch

Solution: If the cause for the JavaScript Void 0 error is a simple glitch, then it is advisable to restart your system and then run the program again.

Cause: JavaScript’s web browser implementation is broken

Solution: If you experience the JavaScript Void 0 error message after the installation of the new browser on your system, then poor installation of the program or program conflict is most likely to be the deep-rooted cause of this error code. To resolve it, uninstall the program and undo the recent changes.

Cause: Active X controls, Java applets, and active scripting, the key components of JavaScript are disabled

Solution: You should know that components including Active X controls, Java applets, and active scripting are all essential to JavaScript in order to make your browsers run properly. If these are disabled, you may come across the JavaScript Void (0). To fix it open your browser and select the Tools tab. Then click the options button and select content. Here check the ‘enable JavaScript’ check box and click Ok to enable these components.

Cause:  Registry Issues

Solution: If after performing all the solutions discussed above, you still come across JavaScript Void (0) error code, then you should know that the problem is bigger than what you expected. It triggers registry issues. Either the cause of the error is misconfigured or invalid registry keys. To reconfigure the registry keys setting may be a challenging task and complex if you are not a computer programmer.

Error Code 0x803f7001 – What is it?

Error code 0x803f7001 occurs when there is a failure to update your Windows operating system to Windows 10. Usually, a message box pops up with the following statement, “Windows is not activated as your previous version of Windows on this device was not activated prior to upgrade to Windows 10.” When this occurs, common symptoms of the error code will manifest themselves:

• Inability to upgrade your Windows operating system to Windows 10
• Message box with error code 0x803f7001

Solution

Error Causes

The cause for error code 0x803f7001 varies. Usually, it occurs for two reasons: 1) when during the process of upgrading to Windows 10, no valid Windows license or product key is found for your device or 2) when a user performs a clean installation of Windows 10. During a clean installation, a new license is usually required to allow you to activate your copy of Windows.

Further Information and Manual Repair

There are two main options available to fix error code 0x803f7001. Usually, the use of a valid product key can help users rectify error code 0x803f7001. You may also try an automated tool to access the best solutions.

Method One: Use a Valid Product Key

A product key is a code containing 25 characters that enable users to activate Windows. You will need to enter the product key in the exact order it appears in order to install your Windows operating system. All users will be able to access this code in an email or on a card within the Windows DVD package they receive upon purchasing a version of the Windows operating system.

To solve error code 0x803f7001, complete the following steps.

• Step one: Click the Start button then select Settings
• Step two: Select Update and Security then Activation
• Step three: Click the Change product key
• Step four: Type in your valid product key. (To do this ensure the 25 characters are accounted for and in the correct order.)

If the issue causing error code 0x803f7001 relates to your product key, then the instructions within method one will rectify the issue. You will be able to install and activate Windows 10. However, if while attempting to update your Windows operating system, the error occurs once more, you will need to follow the instructions in the manual repair below.

You may also consider contacting a Windows repair technician if you are uncertain of your ability to perform the tasks required to fix error code 0x803f7001. This IT professional will be able to use his or her technical knowledge to perform complex manual repair tasks if the need arises.

Method Two: Install an Automated Tool

Automated tools help PC users eliminate common issues such as Windows error codes. To address or rectify error codes like error code 0x8007007b download a powerful automated tool on your machine. This tool enables users to access quick solutions. It also scans for and corrects issues that may result in error codes or poor PC performance.

One of the most useful utilities for advanced users in Windows is the Windows command line or Command Prompt. It is efficient in fixing system files, checking the disk for errors as well as other intensive tasks that are made convenient using this. One of the tasks you can carry out using Command Prompt is repairing the Windows bootup process if it encounters any issues. However, if you tried running the “bootrec/fixboot” command and you receive an error message saying, “Element not found”, read on as this post will guide you in fixing this error. This kind of error in the command line could be due to a damaged BCD or MBE, inactive system partition, or it could also be that there is no drive letter being assigned to the EFI partition. Whichever the case is, here are some possible fixes that should help you resolve the problem.

Option 1 – Try to repair BCD

As mentioned the error could be caused by a damaged BCD and so to fix the problem, you need to repair BCD by following these steps:

• First, make sure that you have a bootable Windows 10 USB drive with you and use it to boot your computer.
• Once you’re on the Welcome Screen, click on Next.
• After that, click on Repair your computer located at the bottom-left portion of the window.
• Then select Troubleshoot > Advanced Options > Command Prompt.
• After you open the Command Prompt window, execute the following command:

bootrec /fixboot

• Afterward, enter the next command below to rename the BCD file:

ren BCD BCD.bak

• Next, type the following command and make sure to replace “b:” with the letter of your bootable drive attached to your computer.

bcdboot c:Windows /l en-us /s b: /f ALL

• Now, wait until the process is completed and restart your computer to successfully apply the changes made.

Option 2 – Try assigning the drive letter to the EFI partition

• Tap the Win + X keys or right-click on the Start button and click on Command Prompt (Admin) to open Command Prompt with admin privileges.
• Then type the following command to start the Diskpart utility:

diskpart

• After that, if you receive a UAC prompt, just click on Yes to proceed.
• Next, type the following command to list all the volumes created on your PC including both types of partitions that are visible to a normal user in the File Explorer as well as the ones created by Windows 10 by default which helps it in storing the boot files and other important system files:

list volume

• Now type the following command to select the desired volume:

select volume number

• Then type the following command to assign a letter to the selected volume:

assign letter=<LETTER>

Note: Make sure to replace “<LETTER>” with the letter you want to allocate to that partition. Afterward, it will assign a letter to the selected volume.

• Reboot your PC to apply the changes made.

Option 3 – Try setting the System Partition to Active

Like the first given option, you also have to make sure that you have a bootable Windows 10 USB drive before you proceed to set the System Partition to Active. Once you have it covered, refer to these steps:

• Boot your computer using the bootable Windows 10 USB drive.
• Next, click Next when you get to the Welcome Screen.
• Then click on Repair your computer located at the bottom left part of the window and select Troubleshoot > Advanced Options > Command Prompt.
• After opening Command Prompt, type the following command and hit Enter to start the Diskpart utility. It is a command line-based utility just like Command Prompt but has a UAC prompt once you provoke it. So if you encounter a UAC prompt, just click on Yes to proceed.

diskpart

• Now type the following command:

list disk

• From there, select your primary disk by typing the following command:

select disk number

• After that, list all the partitions on the selected disk by entering the following command:

list partition

• The command you just entered will list all the partitions created on your PC including both types of partitions that are visible to a normal user in the File Explorer as well as the ones created by Windows 10 by default which helps it in storing the boot files and other important system files.
• Now type the following command to select the partition that is usually around 100 MB in size:

select partition number

• Finally, type the following command to mark the partition active:

active

• Then type the “exit” command to exit the disk part utility.

Well if anyone told me just a few years ago that I will see the day when Microsoft releases a new OS based on Linux I would be very amused, but that day has come. Mariner is the newest OS out of nowhere. Microsoft’s new Linux Distro, dubbed Common Base Linux (CBL)-Mariner, isn’t the type of distro you’d want to install directly on any old machine. It’s primarily meant for cloud infrastructure and edge products. Specifically Microsoft’s Cloud and Edge products. But if you are curious, it’s possible to run. Juan Manuel Rey, a Microsoft Senior Program Manager for Azure VMware, recently published a guide to ISO CBL-Mariner image. With that, you can easily get it up and running. And you can build CBL-Mariner on an Ubuntu 18.04 desktop. So you can try it out since it is free. You can get it from here: https://github.com/microsoft/CBL-Mariner It is obvious that Microsoft aims to set itself as a leader in enterprise server environments with this move and it is very likely that it may succeed or at least give a good shake to its competitors, mainly red hat and Suse which are two dominant distros in that field. Many believe that they can win over by providing regular updates and package delivery via their already established system and that feature could be a turning point for some. In any case, time will tell and we shall see.