You might have experienced a situation where you’re trying to install or update your Java application on your Windows 10 computer but were not able to do so for some reason. One of the problems you can encounter while updating or installing Java is Error Code 1603. There are two ways you can install Java – you have the option to choose where to get Java either from the online download or offline download. There are times when before you can install Java, you might have to disable the firewall first as it may interrupt the Java online installation. And while doing so, if you are getting the “Java Update or Install did not complete – Error Code 1603” error message, read on as this post will show you what you can do to fix it. At the time of writing, the exact cause of this error is still unknown. On the other hand, you must still check if you have fulfilled all the system requirements needed to install Java. You have to make sure that your Windows 10 PC has sufficient disk space available for the Java installation or update. In addition, you also have to make sure that you meet all the hardware requirements and you are using a popular web browser for the installation, and that you have administrative privileges for download and installation. To fix the “Java Update or Install did not complete – Error Code 1603” error, here are some suggestions you can try.

Option 1 – Restart your computer before you install the new Java package

You might have to restart your computer if you got the error code 1603 while installing Java through an offline download.

• Restart your computer.
• Next, download and install the offline installer of the Java package from the official site of Java and not some third-party source.
• In the prompt box that appears while downloading the Java package, select the option Save in and save the package in your preferred folder.
• After that, navigate to the saved, downloaded package on your computer and then double click on the file to begin the installation process.

After that, if it didn’t fix the problem and you’re still getting the error code 1603, follow the next given option below.

Option 2 – Uninstall the old versions of Java before you install the new package

• Open the Control Panel.
• After that, click on Programs and features.
• Then select the old Java package and click on Uninstall.
• Restart your computer and then try installing the new Java package again from its official site.

Option 3 – Disable the Java content in the browser you’re using via Java Control Panel and reinstall Java

• Open the Control Panel again.
• And then click on the Java icon to open the Java Control Panel.
• Next, navigate to the Security tab and then uncheck the “Enable Java content in the browser” option.
• Then click on Apply and then Ok to save the changes made.
• Now install the new Java package again after you download it from its official website.
• Once the installation is completed, re-enable the “Enable Java content in the browser” option in the Java Control Panel as it is essential especially if you are running Java content in your browser.

There are a lot of home users that often get a computer that comes installed with the Windows 10 Home. And since Windows 10 Pro offers more features and utilities compared to Windows 10 Home, a lot of users also prefer to upgrade their Windows 10 Home computers to Windows 10 Pro. However, while doing so, a number of users reported that they encountered error 0xc03f6506 and they were not able to proceed with the upgrade. If you are one of these users, when you encounter error 0xc03f6506, you will see the following error message on your screen:

“The last product key you entered can’t be used on this copy of Windows (0xc03f6506).”

This particular error tends to occur when you go on to activate Windows 10 although it can also appear during the upgrade process. In such cases, you will see the following error message:

“Unable to upgrade your edition, We can’t upgrade your edition of Windows. Try upgrading your edition of Windows again. (0xc03f6506).”

To fix the Activation Error Code 0xc03f6506 in Windows 10, use the options provided below as references but before you proceed, make sure that you create a System Restore point first.

Option 1 – Try to use the Registry Editor

If you have already upgraded from Windows 10 Home to Windows 10 Pro and you’re having trouble with its Activation, then you might want to apply some registry tweaks to fix the problem. How? Refer to these steps:

• Tap the Win + R key combination to open the Run dialog box.
• Then type “Regedit” in the field and click OK or tap Enter to open the Registry Editor.
• Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion
• From there, look for a DWORD named “EditionID” and once you found it, double click on it and change its Value data to Windows 10 Professional.
• After that, look for another DWORD named “ProductName” and double click on it to change its Value data to Windows 10 Professional.
• Once you’re done, restart your computer to apply the changes made successfully.

Option 2 – Try to use Command Prompt

If the registry tweaks you applied didn’t fix the Activation error, then you can try using Command Prompt instead. Note that you can use this option in both scenarios pointed out above.

• First, you have to insert a bootable drive of the Windows10 installer.
• Next, tap the Win + X keys and select Command Prompt (Admin) from the menu.
• After opening Command Prompt as admin, navigate to the root location of the bootable drive inside the Command Prompt command line.
• Once you’re already there, type the following command and tap Enter:

setup.exe /auto upgrade /pkey <YOUR WINDOWS 10 PRO EDITION PRODUCT KEY>

After entering the command, check if it was able to fix the Windows Upgrade or Activation error 0xc03f6506. If not, refer to the next given option below.

Option 3 – Try to disable the Network Adapter

Just like the second option, you can also use this option for both the given scenarios above.

• Tap the Win + X keys and select Network Connections from the menu.
• This will open the settings for your network and on the left side panel, click on the “Change adapter settings” link. This will open Control Panel.
• From there, click on the network your computer is connected to, and then right-click on the Network Adapter that you are using and select Disable.
• After disabling the Network Adapter, try to switch to the edition of your copy of Windows 10 again and see if the problem is now fixed and don’t forget to double click on the disabled Network Adapter to get back on the Network.

As you know, DLL files in the Windows environment contain all the code needed by programs in order to properly function. And like with most other software, the functions in the DLL file have to be compatible with Windows especially if they are using any built-in service. So if you encounter an error that says, “DLL is either not designed to run on Windows or it contains an error”, when you try to launch a program, then this could be due to a compatibility issue. To fix this error, read on as this post will walk you through doing that. Based on the reports of users who encountered this error, the error pointed to a DLL file that was either designed to run on a different version of Windows. It is also possible that the DLL file itself is the problem. Here’s the complete error message:

“Bad Image – DLL file is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.”

According to security experts, the DLL files that are known to trigger this kind of error message are msvcr100.dll, msvcr110.dll, msvcp140.dll, lmirfsclientnp.dll, and so on. To fix this problem, you can try to update or reinstall the program that’s throwing the error to its latest version. You could also ask the vendor for the latest version of the DLL as well as run a System File Checker scan.

Option 1 – Try to update or reinstall the program to its latest version

The first thing you can do to fix the problem is to update or reinstall the program that’s throwing the error. It is possible that the version of DLL might be using a system call that is deprecated. So if you had updated your Windows 10 computer recently, you might want to check for an update of the software or you could also try to reinstall its latest version.

Option 2 – Try asking the vendor for the latest version of the DLL

The next thing you can do to fix the error is to ask for the latest version of DLL from the vendor. There are times when the software uses an open-source version of DLL so it is better if you ask the vendor if there is a DLL file that has to be updated. If there is, then you need to make sure to register the DLL once you have it.

Option 3 – Try to re-register the problematic DLL file

You can also try to re-register the DLL to resolve the problem. The Regsvr32 tool is a command-line utility that can be used to register and unregister OLE controls like DLL and ActiveX (OCX) controls in the Windows operating system. Follow the steps below to use it.

• Open Command Prompt as admin from the WinX menu.
• Next, type the following commands in the elevated Command Prompt and hit Enter to execute the command. This will re-register the affected DLL file using the Windows operating system tool, regsvr32.exe.
  • exe /[DLL file]
  • exe [DLL file]

Note: Replace “[DLL file]” with the name of the DLL file that was pointed out in the error.

• After you execute the given commands, you should see a message saying, “DllRegisterServer in vbscript.dll succeeded” if the Regsvr32 tool was able to run successfully. After that, try to install the program again and see if it now works.

Option 4 – Try to replace the DLL file from a trusted source

• First, you need to get the new DLL file from another computer with preferably the same file version number.
• After that, you need to boot your PC into Safe Mode and navigate to the paths listed below and then replace the file using a USB drive or other external storage devices.
  • x86: This PC > C:/Windows/System32
  • x64: This PC > C:/Windows/SysWOW64
• Next, type “cmd” in the Cortana search box and right-click on Command Prompt, and select “Run as administrator” to open it with administrator privileges.
• Now type the “regsvr32 ntdll.dll” command and hit Enter.
• Restart your PC and check if the error is now fixed.

Option 5 – Run System File Checker scan

If reinstalling the program didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys 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.

 Reboot your computer.

Option 6 – Troubleshoot the isDone.dll error in a Clean Boot State

You can also troubleshoot the “DLL is either not designed to run on Windows or it contains an error” in a Clean Boot state. It could be that there are some third-party applications in your computer that are preventing the application from getting installed and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, make sure that you’re signed in as administrator and then try to install the application again.

Option 7 – Try scanning your computer using Windows Defender

The DLL file might also be infected with malware or virus and to eliminate it which could explain why you’re getting the “DLL is either not designed to run on Windows or it contains an error”. Thus, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

As you can notice in Blue Screen errors, most of them point out a file that’s related to the errors. One of these files is the Storport.sys file which is a system file related to the storage of data in the storage unit of a computer. This file is created by the Microsoft Storage Port Driver. So if this file ends up getting dragged on Blue Screen errors, there can be a number of reasons for why it’s happened. Blue Screen errors related to the Storport.sys file may include conflicts with the hardware, incompatible firmware issues, corrupted drivers, missing or corrupted system files, to name a few. Here are some of the common Blue Screen errors related to the Storport.sys file:

• KMODE_EXCEPTION_NOT_HANDLED
• KERNEL DATA INPAGE
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL
• SYSTEM SERVICE EXCEPTION

Microsoft Windows is the one that provides the Storport.sys file a storage port driver that is suited especially for the use of high-performance buses like fiber channel buses and RAID adapters. There are a number of advantages in using Storport instead of the SCSI Port, according to Microsoft:

• “Improved performance, both in terms of throughput and the system resources that are utilized.
• Improved Miniport driver interface that addresses the needs of high-end storage vendors, particularly host-based RAID and fiber channel vendors.”

If you encounter any of the above-mentioned Blue Screen of Death errors, then here are some troubleshooting options that might help but before you get to them, you can try to perform a System Restore first especially if you have the habit of creating System Restore points. This might fix the problem. To perform a system restore, refer to these steps:

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

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first. In addition, you also have to boot into Safe Mode with Networking before you carry out the troubleshooting steps below.

Option 1 – Try to update or rollback your device drivers

The first thing you can try to fix the Storport.sys Blue Screen error is 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. Note that the main drivers that might be the cause behind the Storport.sys Blue Screen error will be listed under the “ID ATA/ATAPI controllers” section as well as the “Storage controllers” section.
• 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 also directly download the relevant drivers of your computer from the manufacturers’ website. So if you have an SSD, the issue might be due to an old storage driver. Option 2 – Try to recreate the Storport.sys file If the first option didn’t work, the next thing you can do is to recreate the Storport.sys file. Every time your Windows 10 PC boots up, it looks for all the system drivers in place and if it is unable to find them, it tries to create them. This is why if you remove your corrupt driver file, chances are, you might get a fixed file recreated just for you. How? Refer to the steps below.

• Boot your Windows 10 PC in Safe Mode.
• Then open File Explorer and navigate to this location: C:/Windows/System32/drivers
• From there, look for the file named sys and rename it to Storport.old.

Note: As you can see, the file’s extension has changed from .sys to .old.

• Now restart your computer and check if the Storport.sys Blue Screen error is now fixed.

Option 3 – Run System File Checker or SFC scan

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

 Reboot your PC.

Option 4 – Try to run the DISM commands

You might want to repair potentially corrupted files in your system as having them could also trigger the Storport.sys Blue Screen error. To repair these corrupted system files, you can run the DISM commands:

• 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 and check if the dxgkrnl.sys Blue Screen error is now fixed.

Option 5 – Run the Blue Screen Troubleshooter

Troubleshooting Blue Screen of Death errors wouldn’t be complete without the Blue Screen troubleshooter. As you know, it is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Storport.sys. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

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

The new razer modular table looks like something that came out from Star Trek. Project Sophia is a desk but, it is a special kind of desk. It comes with modules that attach themselves underneath the table itself for customization purposes so each user can somewhat create a layout on the table itself as he or she desires. The table itself comes packed with intel CPU and Nvidia GPU but it is said that this component and PC parts will overall be easily upgraded to different ones as users desires. The table itself looks very basic and it comes with a very large OLED screen between two different sizes depending on your table choice. You can choose between 65” or 77” screen sizes and OLED is mounted on the table itself so you cannot move it or adjust the angle of it that I somewhat find annoying but that comes from th4e fact I am used to adjusting my screens, but for this large screen maybe you do not need to adjust its rotation in order to get best viewing angle. Modules themselves will offer some on-the-fly information and quick settings for the PC itself while being modular in a sense they could be mounted in different positions on the table itself providing some customization and order to suit users needs. Modules, for now, are: THX Spatial Surround Sound Controls, system monitoring, programmable hotkey module, Thunderbolt™ Powered eGPU, RAID Controller, Network Performance Module, 15W Wireless Charger, Thunderbolt™ 4 Hub, Media Controls. Of course table, itself will have Razer chroma RGB on its surface and Razer says it will have a total of 13 different modules available on launch for a true level of personalization.

Conclusion

Is this Razer table something that you really need or just another expensive toy? Personally, I would not mind this table at all but I would choose modules for work, not gaming. Having some things like media controls or RAID controllers all the time at your fingertips is a great time saver and productivity asset. Razer also advertises some modules and setup already for streamers, creators, or team members and has some according modules like touch screen digitizer with stylus and similar.

The latest update from Panos Panay on Twitter is including New and redesigned Snipping tool inside Windows 11. From the shared video, we can see that it includes modern Windows 11 UI redesign and it looks and feels like a part of Windows 11. More things that can be seen from the shared video is that it looks like the new snipping tool is a merged version of the old with snip & sketch. It is good to see that it is still possible to capture screen with easier way natively inside Windows 11 but some more functionality would be more welcome I guess. Users were asking for added functions for a long time like adding simple text for example but from shared video, no new features were presented so for some users 3^rd party solutions will still be the way to go. The new and redesigned Snipping tool will roll out with the next update and we will see then about all new features inside it firsthand. Until then, take care.

As you know, Microsoft constantly releases new updates with the main goal of fixing bugs as well as deliver users with new and exciting features. However, there are times when the latest update comes with an unwanted bug. One of these bugs is an error message saying, “Low Disk Space. You are running out of disk space on Local Disk (G:). Click here to see if you can free space on this drive.” So if you have recently installed a Windows 10 update, then you’ll most likely see a completely new drive on your computer which will appear right after the installation of the update and you’ll also start seeing the aforementioned error message. It gets irritating as this error message keeps on popping up even if you still have a lot of free space on your other drivers. Obviously, the main reason why this error message pops up all the time is the bug brought along by the Windows Update. This bug unhides the recovery partition drive and allocates it a drive letter which is why you are seeing a new drive in your computer. Thus, you can get rid of the pesky error message by simply removing the letter of the new drive. Just remember that you must not delete anything from the recovery partition drive nor format the drive. Formatting or deleting the recovery partition drive can heavily affect the recovery of Windows since the data on the drive is used by the Windows Recovery Environment or your system’s manufacturer. A lot of users have reported that removing the drive letter has resolved the issue. And if you worry that removing the drive letter will delete the drive, you are mistaken. This solution is basically harmless and is proven effective to make the notifications go away. Carefully follow the instructions below to get rid of the Low Disk Space notification by removing the drive letter.

• Step 1: Tap the Windows key once.
• Step 2: Next. In the Windows Start Search, type in “command prompt” and right-click on Command Prompt from the search results and select the “Run as administrator” option or you could simply tap Win + R keys and then input “cmd” and hit Enter to open Command Prompt.
• Step 3: After opening Command Prompt, type in “diskpart” and tap Enter.
• Step 4: Next, type in “list volume” and tap Enter. After that, you will see a list of drives.
• Step 5: Take note of the letter associated with the newly created drive.
• Step 6: Afterwards, type in “select volume <drive letter>” and tap Enter. Take note that you must replace the <drive letter> with the drive letter you’ve found in Step 5.
• Step 7: Now type in “remove letter=<drive letter>” and then tap Enter. Once again, replace the <drive letter> with the letter you took note of in Step 5.

Anytime when a new folder is created in Windows name "New Folder" is offered and set as the default name. If by any chance you would like to change this and set your own default name instead of the standard one, follow this guide. Please be aware that this guide will require you to change the registry of Windows, it is common practice to make a backup of your registry each time you want to manually change any values in it, just in case something goes wrong.

• In order to change the default new folder name first press ⊞ WINDOWS + R to open the run dialog, type in it RegEdit, and press ENTER
• In registry editor find the key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer

• Select the NamingTemplates key. If it is not present, you’ll need to create one.
• Right-click the NamingTemplates key to add a String Value.
• Assign it the following name: RenameNameTemplate.
• Double-click on the RenameNameTemplate data value to open the Edit String dialog box.
• In the Value Data field enter the new text you want to appear when you create a new folder. You have to make sure you are not using any of the following characters: \ / ? : * " > < |
• Close the Registry Editor and Exit.
• Now, when you create a new folder, it will be named Whatever you chose instead of the New folder.

And that is all to it, you now have your own personal new folder naming template.

If you have a BlueTooth device on your computer, you know that each time you need to receive or transfer the file you need to find the icon in the system tray, right-click on it and choose the desired option. But there is a simpler solution, create a Bluetooth icon on the desktop so it is always easy to access. Open File Explorer by pressing ⊞ WINDOWS + E Go to C:\Windows\System32 Find fsquirt.exe Right-click on it and choose copy Go to the desktop and right-click, choose paste Rename the file to Bluetooth And, you are done!

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.