5 Windows 10 Upgrade errors you might encounter

As you know, USB is now being widely used in all devices with USB A as the leading type with most devices based on it. Peripheral devices such as Pen Drives, External Hard disks, and many more also use a USB port. On the other hand, USB C is also coming up to be the next big standard in the computing world because of its high transfer speeds, wider compatibility as well as support for external Graphics Processing Units. However, just recently, USB 3.0 ports have been reported to cause the following error to pop up on Windows 10 computers every time a USB device is plugged in.

“Not enough USB controller resources. The controller does not have enough resources for this device.”

To fix this error, here are some guidelines you can check out. Make sure to follow them carefully.

Option 1 – Try to use a lower generation USB port

The first thing you can do is to try using a lower generation USB port as this issue mostly occurs when a device is connected to a USB 3,0 port. This means that you have to plug in your device to a USB 2.0 port and then see if it fixes the error or not. You can easily decipher a USB 3.0 port from a USB 2.0 port as the former is in blue.

Option 2 – Try to use a dock

You could also try to use a dock to resolve the error. Note that when too much power on laptops and notebooks are drawn from the USB ports and as a USB 3.0 port draws more power compared to a USB 2.0 port. Thus, if you plug in your USB storage device into a USB 2.0 port with the help of a dock, it should fix the problem.

Option 3 – Try disabling the xHCI Mode option in the BIOS

• First, boot your computer into the BIOS.
• Once your computer has booted, go to the Advanced tab.
• Next, make sure that the entry for “xHCI Pre-boot mode” is set to Disabled under the USB Configuration section.
• Now save the changes you’ve made and then restart your computer to Windows 10 and see if the error is now fixed.

Option 4 – Update or reinstall the Universal Serial Bus Controller driver

Since it could be a driver issue, you can try to update or reinstall the Universal Serial Bus Controller drivers using the Device Manager. Refer to the following steps:

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right click on each one of the USB drivers, especially the Generic USB Hub driver, and then select the Update Driver from the menu.
• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 5 – Run the Hardware and Devices Troubleshooter

You could also run the Hardware and device Troubleshooter to try and fix the “Not enough USB controller resources” error.

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Hello and welcome to our Business Email Etiquette. Most people have experience in writing emails at some point before in their lives. However, the emails an average person writes are probably personal emails and not mails for work purposes. Emails you send to friends are incredibly different in content and context to business emails you would send to customers or employers or even other colleagues in your workforce. So, if you have a job that involves you writing emails to people in business style, learning business email etiquette is an absolute must for you.

 1. Heading layouts

When you are sending emails to friends, you generally lay them out like a memo. This means there is very little detail in the layout besides basic greetings and paragraphs, usually starting with the greetings. However, with a business email, it is best to lay it out exactly like you would lay out a formal letter. You need to put the company’s address in the right-hand corner and the date as well. Only then must you go on to the greetings. This will make your email look more formal, making you seem like a professional who knows what they are doing as opposed to someone who just couldn’t be bothered spending the extra time to get the layout right.

 2. Proper greetings

 When you are sending an email to a friend, you usually greet them informally. If their name was Mary Johnson, you’d probably start your letter with a ‘Hey Mary’ or a ‘Hello Mary.’ However, this is not considered a professional way to write an email to a customer or other important person in your business. Again, you must use the proper method that you would greet someone with were you writing them a formal letter instead. If your customer is Mary Johnson again, you should greet her with respect. ‘Dear Ms. Johnson’ would be the most appropriate way to start off your letter’s actual body in this case. If you do not know the recipient’s name, then you should start with a simple ‘Dear Sir or Madam.’ Politeness will always get you incredibly far, no matter what line of work you are in.

 3. Informal language

 You should get straight to the point with your email. Don’t dawdle on with it like you would if chatting to a friend and don’t write it how you would speak either. You use language that sounds impressive and smart while not using such obscure language that your recipient doesn’t know what you are saying. All the time, you must keep it informal where possible, possibly even impersonal as well. It will make you seem very professional in the long run.

 4. Signing off

When you are sending your email, you must end it as you would with a letter also. Don’t just say ‘Bye’ and your first name; that is too personal. You need to say ‘yours sincerely if you know the name of the recipient and ‘yours faithfully’ if you do not. Then you should end with your full name and whatever position you have at the company. (CEO, technical staff etc.) So there you have it! All you need to do now is to show your boss that you can handle the emails from now on!

Code 0x80200056 – What is it?

The Error Code 0x80200056 will appear in a few different instances, though always applies to an interrupted download.   Windows 10 will quickly discover that their upgrade and/or download did not work correctly. Not every user who upgrades to Microsoft Windows 10 will face this issue, only a select few random instances will occur. Common symptoms include:

• A dialog box appears with the Error Code 0x80200056
• Microsoft Windows 10 upgrade is unsuccessful
• Users are unable to open any applications after completing the Microsoft Windows 10 install

Solution

Error Causes

This error can be caused by a number of common problems, the first of which is the easiest to diagnose.

• If during the upgrade process, you accidentally restarted your PC, or inadvertently signed out of your PC, the error will occur.
• Third-party software conflicts can cause this error message during the Microsoft Windows 10 upgrade.
• Error Code 0x80200056 may also appear if you have corrupted system files on your PC.
• A change in date and time during the Microsoft Windows 10 upgrade could potentially cause this error.

None of these causes should overtly affect the operation of your PC, but merely prevent the upgrade and/or download from functioning correctly. If your PC is exhibiting other operating system errors in addition to Error Code 0x80200056, it would be wise to contact Microsoft Support before the issues lead to a possible catastrophic failure.

Further Information and Manual Repair

With the very recent release of Microsoft Windows 10, we are seeing a number of users discuss Error Code 0x80200056. Luckily, there are three different methods that any home user can perform to alleviate the error and complete the Microsoft Windows 10 download successfully.

Method 1

Use if your PC restarted accidentally during the upgrade, or if you accidentally signed out of Windows during the upgrade.

1. Make sure that your PC or Laptop is plugged in, to avoid another accidental restart.
2. Turn your PC on, or make sure that it is running. (Close any and all unnecessary programs)
3. Attempt the upgrade again, you should be able to run the upgrade successfully without further issue.

The following solution methods will apply if corrupted files, date/time changes, or third-party software interference is the issue causing Error Code 0x80200056.

Method 2

The following solution methods will apply if corrupted files, date/time changes, or third-party software interference is the issue causing Error Code 0x80200056.

1. Click on your “start” icon and choose the CMD (command prompt) option.
2. Right-click on “command prompt” and choose “run as administrator”.
3. Paste the command “bitsadmin.exe /reset /allusers” into the command prompt and press ENTER.
4. Restart your PC and attempt the Microsoft Windows 10 upgrade again.

Method 3

1. Click on your “start” icon and choose the CMD (command prompt) option.
2. Select “run as administrator” (enter a password if asked to do so).
3. Enter the following command into the command prompt- “sfc/scannow”, press ENTER.
4. Do not close the command prompt window until the entire process is complete.
5. The scan will determine if you have any missing or corrupted files. You will receive a message that says either: “Windows Resource Protection did not find any integrity violations”.Or “Windows Resource Protection could not perform the requested operation”.
6. If you received the first message, then your files are fine. The second message indicates that there are file corruption issues.
7. To repair the disjointed files, restart your PC in SAFE MODE, and reopen the command prompt window.
8. Enter the following command into the command prompt- “sfc/scannow”, press ENTER.
9. After the scan is run again, you will receive a message stating that the files have been successfully repaired.
10. Restart your PC in normal mode and start the Microsoft Windows 10 upgrade again.

To use a powerful tool to resolve Windows 10 upgrade Error Code 0x80200056 issue, download a powerful tool. Click here to download Restoro. If any of these methods do not allow for the successful upgrading of your Windows system, contact the Microsoft Support team. Make sure to include in your message to support what fixes you have attempted, and what the outcomes were. As Microsoft Windows 10 is so incredibly new, there are bound to be issued while the program is in its infancy. Fortunately, a majority of these issues should be worked out by Microsoft relatively quickly.

Runtime Error 713 is an error that occurs during the distribution of a Visual Basic application that includes a data report. The error is displayed on the screen when you try to open the data report from your desired application.

Error Causes

The reason why computer users often experience the Runtime Error 713 is that the data report run-time file also referred to as Msdbrptr.dll is not included in your setup package. Though this error does not pose any big threat to your computer, however, it is recommended to fix the error because the Runtime error 713 may hamper your ability to install and access new programs.

Further Information and Manual Repair

Don’t you panic if you see Runtime Error 713 message pop up on your PC? This error is rated easy to repair and can be fixed in a couple of minutes. There are two ways to fix Runtime Error 713. You can choose whichever 2 alternatives suit you best.

• Method 1

First, open your project and include a reference to the data report file, the Msdbrptr.dll file. Locating this file is not difficult. It is listed as Microsoft Data Report Designer v6.0 in the reference dialog box. Sometimes you may see this file listed more than once. Now when this happens be sure to select the file that is associated with Msdbrptr.dll. After you select it, the reference will be verified. Once verification is complete, you are good to go. Now you can try rebuilding your setup package again.

• Method 2

The second alternative is to add the Msdbrptr.dll file manually in PDW (the Package and Deployment Wizard). Simply add the file in the Included Files dialog box window and run the PDW. Now you are all set to rebuild your setup package. Whether you follow method 1 or 2 after you rebuild the setup package and the installation is complete, you will see the following files in the indicated folders:

• <windows system>Msdbrptr.dll
• <program files>Common Files\Designers\Msderun.dll
• <windows system>Msstdfmt.dll

The presence of these files indicates successful installation and now you can easily try opening the data report. If you’ve noticed, all you have to do to fix Runtime Error 713 was to include the Msdbrptr.dll file. So, next time if you or your friends experience Runtime Error 713, you know exactly what to do and how to fix it.

Steam is one of if not the largest online store for the digital distribution of games on the PC platform. The game gets downloaded to your PC when you are planning to play it and its saves are synched in the Steam cloud. They get automatically downloaded when you install the game but you can also get your saves by directly downloading them from Valve's website in your browser. If Steam isn’t automatically downloading your old save games after you install a game, ensure Steam Cloud is enabled for that game within Steam. Locate the game in your Steam library, right-click it, and then select Properties. Click the Updates tab and ensure the Enable Steam Cloud synchronization option is checked for the game. If this option isn’t checked, Steam won’t automatically download your cloud saves. If you don’t see a Steam Cloud option for a game here, that game doesn’t support Steam Cloud. Not all games on Steam do, it’s up to each game developer.

Download the Files in Your Web Browser

Valve lets you download your Steam cloud save files via a web browser, too. You can download just your saved files without re-downloading the entire game. To find your saved files, visit Valve’s View Steam Cloud page in your web browser and sign in with your Steam account. You’ll see a list of games using your Steam Cloud storage. Locate the game in the list and click Show Files to see all the files for a game. Each game has a page showing all the files it’s storing in Steam Cloud, as well as the date they were modified. To download a file, click Download. Download all the save files for your game, and you’ll have a copy of its save games. This feature is especially useful for multi-platform games that don’t automatically synchronize save files between platforms.

If you encounter the BAD_SYSTEM_CONFIG_INFO Blue Screen error in your Windows 10 PC, then read on as this post will guide you in fixing this issue. Usually, this kind of Blue Screen error is caused by some issues with the Boot Configuration Data file. The main issue inside of the Boot Configuration Data file is that either some boot order files or older files might be in conflict with the newer ones or the stable ones and thus triggering the BAD SYSTEM CONFIG INFO Blue Screen error. This kind of Stop error also indicates that there is an error in the Windows Registry which is why you need to update potential culprit drivers as well as edit some entries in the Registry if need be. But before you get started, make sure that you create a System Restore Point first. After creating a System Restore Point, try to boot your computer into Safe Mode and then restart your computer normally. However, if it doesn’t work, proceed to the given options below.

Option 1 – Run System Restore

Performing System Restore might help you in fixing the BAD SYSTEM CONFIG INFO Blue Screen error. 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.

Option 2 – Update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or roll back the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and 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.

Option 3 – Try fixing the Windows Registry files

In order to fix the Windows Registry files, you need to make a bootable Windows 10 USB drive and then boot your PC using it. To do so, refer to the steps below.

• Once you see the Welcome Screen, click on Next.
• Then click on the “Repair your computer” option located on the bottom-left section of the window.
• Next, click on Troubleshoot > Advanced Options > Command Prompt.
• After opening Command Prompt, execute each one of the commands listed below in the sequence that they are given:
  • CD C:WindowsSystem32config
  • ren C:WindowsSystem32configDEFAULT DEFAULT.old
  • ren C:WindowsSystem32configSAM SAM.old
  • ren C:WindowsSystem32configSECURITY SECURITY.old
  • ren C:WindowsSystem32configSOFTWARE SOFTWARE.old
  • ren C:WindowsSystem32configSYSTEM SYSTEM.old
• After executing the commands given above, type in the next ones below and make sure to execute them in the given sequence below.
  • copy C:WindowsSystem32configRegBackDEFAULT C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSAM C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSECURITY C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSYSTEM C:WindowsSystem32config
  • copy C:WindowsSystem32configRegBackSOFTWARE C:WindowsSystem32config
• Now type “exit” to close Command Prompt.
• Restart your PC for the changes to take effect.

Option 4 – Run a Memory Check to test RAM

On the other hand, you can also fix the BAD SYSTEM CONFIG INFO Blue Screen error by running a Memory Check using the Windows Memory Diagnostic. Refer to these steps to do so.

• Tap the Win + R keys to open the Run dialog box.
• Then type “mdsched.exe” in the field and hit Enter to open the Windows Memory Diagnostic.
• After that, the Windows Memory Diagnostic will give out two options such as:

1. Restart now and check for problems (recommended)
2. Check for problems the next time I start my computer

• Select any of the given options. After that, your computer will restart and check for memory-based issues upon the restart. If there are any issues, it will automatically them.

Option 5 – Rebuild BCD files and repair MBR files

Like what you did on the third option above, you also have to make a bootable Windows 10 USB drive for this option and then boot your Windows 10 PC using it.

• Once you get to the Welcome Screen part, click on Next.
• Afterward, click on the Repair your computer option located on the bottom-left part of the window.
• Then click on Troubleshoot.
• Next, select the Advanced Options and then Command Prompt.
• Once Command Prompt has been pulled up, enter each one of the following commands and in the sequence that they are given to rebuild BCD files and repair MBR files:
  • bootrec /repairbcd
  • bootrec /osscan
  • bootrec /repairmbr

• Now type “exit” to close Command Prompt and then restart your computer to successfully apply the changes made.

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.

Shortcut virus is an easily spreadable and annoying combination of Worm and Trojan that hides all of your files and folders and then replaces them with shortcuts that look identical to replaced files and folders. Once disguised it will wait patiently for a user's click and once that happens it will replicate itself and further infect the system. This rapid spread can lead to stolen personal data, some system hick-ups, and other system-related issues. This malware mainly affects physical file transfer devices like for example and most USB drives, hard drives, and SD memory cards and it can easily transfer itself to the computer. The advantage of this shortcut virus comparing it to others is that it is mostly undetected by a vast variety of antivirus software. So running just anti-virus software maybe not be enough to remove it from your system. Luckily for all unfortunate users that have caught this annoyance, it can be easily removed fully manually in a short time.

How to Remove Virus from USB and other removable media

Firstly plugin USB, SD, or removable drive. The infection will transfer to your computer when the infected drive is plugged in so before we go to clean the computer itself, clean each removable drive that you have. Also know that infection will spread from computers into removable devices as well if it is not cleaned. Open the File Explorer and remember under which letter is removable drive registered. Open Command prompt but with administrator privileges and go to infected rive by typing its letter followed with “:” (for example D:) and press ENTER Once you have successfully gone to infected drive type in command prompt: Attrib -s -r -h /s /d *.* This will unlock all original files back into removable storage, next copy all files to your computer, and format the removable drive. Once the format is complete, unplug the removable device. Continue to clean all devices with the same method.

How to Permanently Remove a Shortcut Virus from Your PC

Now once we have cleaned all removable devices it is time to fully clean the PC Firstly open the task manager ( CTRL + SHIFT + ESC ), in the process tab find wscript.exe or wscript.vbs, right-click on it (or both if present), and select End Task. Now close the task manager and press Start. Inside start typing in registry editor to search for it and once found open it. Find the following key inside the registry editor: HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/Run In the right panel, look for any strange-looking key names, such as odwcamszas, WXCKYz, OUzzckky, etc. For each one, run a Google search to see if it's related to shortcut viruses. If any returns a positive match, right-click on them and select Delete. !!! Accidentally deleting an important key can cause Windows to become unstable, so double-check everything !!!. Close the Registry Editor Now press ⊞ WINDOWS + R to open the run dialog and type in it Msconfig followed by ENTER. Once the System Configuration window opens go to the Startup tab. In the Startup tab, look for any strange-looking .EXE or .VBS programs, select each one and click Disable. Close the Window. Once again open the run dialog and type inside %TEMP% and press ENTER in order to open the Windows temp folder. Inside this folder delete everything. Next in the File explorer go to C:\Users\[username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup Look for any strange-looking .EXE or .VBS files and delete them.

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”

Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

PrintNightmare vulnerability has been a struggling issue for Microsoft in the past weeks, each time it seems to be addressed and fixed something new popped up and it still had issues. Microsoft finally addressed the issue but with a price. The default behavior of Point and Print is changed. From this fix onward, the Point and Print driver installation and update behavior will require administrator privileges, which should prevent the exploit to the Windows Print Spooler that could be used by malicious individuals to gain administrative privileges in Windows. The drawback of this fix from Microsoft is that non-elevated users may have difficulty adding or updating printers. Microsoft feels that the security risks caused by PrintNightmare are worth the tradeoff, though. If you really want to let non-elevated users add printers, you can follow the instructions in this Microsoft Support article to disable this mitigation with a registry key. However, doing so will expose you to this known vulnerability and isn’t recommend.