Removing Default Taskbar Buttons in Windows 11

Error 504 - What is it?

Error 504 is a type of runtime error that occurs on Windows PC. A runtime error is a bug that causes software or hardware problems thereby preventing programs from working on your PC correctly. This error may occur during the execution of the program.  It also slows down your PC performance.

Solution

Error Causes

Error 504 can be triggered by many causes such as:

• Incompatibility between 2 software programs
• Malicious software
• Missing DLL files
• Registry issues

Further Information and Manual Repair

Whenever you experience the error 504 on your system, it is advisable to resolve it immediately, typically because runtime errors like error 504 can lead to system failure and valuable data loss which is more than often hard to recover. To resolve this error code, you don’t necessarily have to hire a professional for the job. In fact, here are some solutions that you can try to fix by yourself, even if you are not a computer programmer.

1. Get the latest updates for Windows and for the program showing the error

This is a quick way to resolve runtime error 504 on Windows PC. To update the latest updates for Windows and for the program causing the error, open Windows Update by going to the start menu. In the search box type ‘update’ and then in the list of results click Windows Update.  In the left pane click on check for updates, wait while Windows looks for the latest updates. It will show you a list of updates available select the important updates that you want to install. Then click ok and then click install updates. After the updates are successfully complete, restart your PC and try running the application. If the error still persists, then try the solution given below.

2. Scan For Malicious Software

Sometimes the runtime error 504 may occur due to viral infection and malware. So, to resolve it download an antivirus. However, the antivirus can also slow down your PC performance.

3. Scan for Registry Issues

Another way to resolve it is to scan for registry issues. The registry and DLL files get damaged when it overloads with too much data. This particularly includes irrelevant and obsolete files. Registry issues trigger runtime errors like 504. The best way to resolve it is to download Restoro. This is an advanced and multi-functional PC Fixer embedded with multiple utilities like a registry cleaner, an antivirus, and a system optimizer. The registry cleaning utility resolves registry issues by removing the unnecessary files completely and repairing the damaged dll files. The antivirus module scans and removes all kinds of malicious software on your PC like viruses and Trojans, thereby resolving the runtime error 504 in seconds. As for speed, Restoro also functions as a system optimizer which boosts the performance of your system significantly. Restoro is safe and bug-free software. It has simple navigation and a user-friendly interface which makes it very easy to operate and workaround. It is compatible with all Windows versions. Click here to download Restoro and resolve error 504 today!

Windows 11 brought with it a simplified right-click menu that has limited options. If you would like to bring the old Windows 10 right-click menu you will have to do some registry tweaking but it is doable. Since this requires registry tweak, please follow given solution step by step

1. Press Start and type RegEdit
2. Click on Registry Editor
3. Inside registry editor find next key: Computer\H_KEY_CURRENT_USER\SOFTWARE\CLASSES\CLSID\
4. Right click in the right part of editor window and select New > Key
5. Type in as a name: {86ca1aa0-34aa-4e8b-a509-50c905bae2a2}
6. Right click on {86ca1aa0-34aa-4e8b-a509-50c905bae2a2} key and select New > Key again to create new key inside this one
7. Name inside key InprocServer32
8. Double click the “(Default)” key in InprocServer32 to open it
9. When the Default key opens close it without making any changes by clicking on OK. This will make its value property Blank instead of value not set
10. Close Registry Editor
11. Restart your PC

Once the system is up if the followed solution is applied you will now have an old school menu once right-click is used.

5 Windows 10 Upgrade Errors

The recently released Windows 10 captivated the mass but its rollout, polished as it might have been, proved everything but seamless. Surf the Internet and you’ll get the gist. People are complaining and they need assistance. Assistance with what you might ask? Many have attempted to make an upgrade but failed after encountering various strange combinations of letters and numbers. These are none other than error codes. If you’ve tried and failed, feast your visuals below as you might encounter one of these 5 Windows 10 Upgrade errors.

Error Code 0x80073712

Encountering error code 0x80073712 in no way implies that you need to throw out your computer system and acquire a new one. Not at all! This error code simply means that a very important file to Windows might have gone missing or corrupted. This file is crucial to Windows update so without obtaining this file, you won’t be able to proceed with the update.

Error Code 0x800F0923

Likely, there are many programs and drivers installed on your computer. They all play a vital role. However, if you’ve received error code 0x800F0923, it might be time to consider or turn your eyes to installed drivers on your system. Why? Error code 0x800F0923 means that there’s a driver or driver on your current Operating System that’s not compatible with Windows 10. There’s clearly a dilemma here.

“We couldn't complete the updates. Undoing changes. Don't turn off your computer.” Or “Failure configuring Windows Updates. Reverting changes”

That’s a pretty odd error but I will say it's slick… That Windows 10 upgrade error is straightforward. Microsoft is just letting you know that they won’t be able to complete the update to Windows 10 and so they are putting your computer back to where it was. How nice of them.

The error messages above are pretty generic and will manifest when the upgrade fails for one reason or the other. To resolve this issue, you’ll most definitely have to decipher what error code was presented. Identifying that will provide a glimpse into exactly what steps you need to take.

The Update Isn't Applicable to Your Computer

I don’t know about you but I strongly believe Microsoft is subtly letting you know that your computer system is old and needs to be thrown out. Also, this update could imply that your PC needs to install important updates to rev you up to the requirements. All relevant updates to your computer must be installed before you can get past this stage.

Error… “Something Happened”

This Windows 10 upgrade error has been the talk of the Internet. In fact, users of Windows OS have been making it a mockery. Clearly, not many have had success after encountering this error. Obviously, “something happened” but it’s just not easy to decipher what went wrong. Microsoft is still trying to figure it out.

Solution

When you have to connect to a drive that’s on a different computer or on external storage, that’s where the mapped network drives come in. Mapped network drives make accessing files a lot easier. However, there are times when it won’t work for some reason. Windows will notify you about the unavailability of mapped network drives in several ways. For one, Windows might display a red X on the network drives or it could be that its status will be unavailable when you try to use it from the Command Prompt or via a notification. It is recommended that you run a few scripts when you log in to your PC as it may so happen that the network drive takes more than usual to connect. Before you start troubleshooting the problem using the given options below, keep in mind that some workouts might only work under certain scenarios. You might need some network access at logon or you might need access to the Group Policy settings. So you need to choose what you prefer more. You can try the given workarounds below if the mapped network drives are not showing or connecting or working on your Windows 10 computer. These workarounds use scripts to make sure that you are connected to them as soon as you start to use your PC. As mentioned, before you can troubleshoot, you need to create scripts first. There are two scripts here namely MapDrives.ps1 which is executed by the second script named MapDrives.cmd and is done at a regular and non-elevated Command Prompt. Follow the steps below to get started.

• You have to create a script file named “MapDrives.cmd” first and then save it on a place where the files are safe. To do that, open a text editor like Notepad and then copy and paste the following script:

PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted" >> "%TEMP%StartupLog.txt" 2>&1 PowerShell -File "%SystemDrive%ScriptsMapDrives.ps1" >> "%TEMP%StartupLog.txt" 2>&1

• After that, save the file and name it “MapDrives.cmd”.
• Next, create a script file named “MapDrives.ps1” and then copy and paste the following content. Just make sure to save both scripts in the same folder.

$i=3 while($True){     $error.clear()     $MappedDrives = Get-SmbMapping |where -property Status -Value Unavailable -EQ | select LocalPath,RemotePath     foreach( $MappedDrive in $MappedDrives)     {         try {             New-SmbMapping -LocalPath $MappedDrive.LocalPath -RemotePath $MappedDrive.RemotePath -Persistent $True         } catch {             Write-Host "There was an error mapping $MappedDrive.RemotePath to $MappedDrive.LocalPath"         }     }     $i = $i - 1     if($error.Count -eq 0 -Or $i -eq 0) {break}     Start-Sleep -Seconds 30 } Note: Now that you’ve created the script files, it’s time for you to proceed to the options given below.

Option 1 – Try creating a startup item

Note that this option only works on devices that have network access at login. So if it’s not there, the script will fail to reconnect the network drivers automatically. To create a startup item, here’s what you have to do:

• Open the Startup folder located at %ProgramData%MicrosoftWindowsStart MenuProgramsStartUp.
• From there, copy and paste the MapDrives.cmd.
• After that, open the Scripts folder located at %SystemDrive%Scripts copy-paste MapDrives.ps1 and then copy and paste MapDrives.ps1 in there.

Note: After you complete the steps above, a log file named “StartupLog.txt” will be created in the %TEMP% folder. Now all that’s left for you to do is to log out of your computer and then log back in. This will ensure that the mapped drives are open.

Option 2 – Create a scheduled task

It is possible to create a scheduled task that runs as soon as you log in to your computer. To create a scheduled task, follow the steps below.

• You have to copy the MapDrives.ps1 script file to the scripts folder of Windows located at %SystemDrive%Scripts.
• After that, open the Task Scheduler and select Action > Create Task.
• Next, type a name and description of the task in the General tab.
• Then click on the Change User or Group button and select a local user group and click OK.
• Now check the box labeled “Run with highest privileges” and switch to the Triggers tab.
• From there, create a new trigger with the “At Logon” option in the Begin the task drop-down menu and then click OK.
• After that, switch to the Actions tab and create a new action then choose to Start a program.
• Next, type “Powershell.exe” in the Program/Script field, and in the Add arguments (optional) field, type the following:

-windowsstyle hidden -command .MapDrives.ps1 >> %TEMP%StartupLog.txt 2>&1

• And in the Start in the (optional) field, type “%SystemDrive%Scripts” as the location of the script file.
• Now under the Conditions tab, select the “Start only if the following network connection is available” option and then select Any connection and click OK.
• Restart your computer or log off from your account and then log back in so that the task will be executed.

Option 3 – Use the Group Policy settings

You need this option if the mapped network drives are defined via Group Policy settings. You have to update the action of the drive maps to Replace. As a result, it will delete the existing mapped drive and create the mapping on each logon again. However, any settings on the mapped drive that are changed from the Group Policy settings will be gone on each logon. So if the changes don’t work, you need to run the gpupdate command together with the /force parameter in order to refresh the Group Policy setting quickly.

Interrupts are designed so that the resource requests don’t get into a headlock when it comes to the hardware level. To simply put it, it is used to break a loop that never ends. Aside from that, developers also designed levels in order to prioritize interrupts. It is also known as “Interrupt Request Level” or IRQL. And if you suddenly encounter a “Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL” error, this means that a driver has accessed a memory location illegally while NT is operating at a specific IRQL. The Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL is a fatal driver coding error and as an end-user, there isn’t much that you can do to resolve it but if you’re a developer, then this means that your code is trying to access an invalid memory location. You could check on different parameters such as memory location that was referenced and code addressed which referenced memory. The technical parameters are:

• a memory location that was referenced
• IRQL at time of reference
• 0 = read, 1 = write
• code addressed which referenced memory

As mentioned earlier, if you are an end-user, there is nothing much that you can do to resolve this problem, but worry not for there are still possible solutions that could help you in fixing it. Refer to the suggestions laid out below to fix Bugcode 0xA –IRQL_NOT_LESS_OR_EQUAL error.

Option 1 – Try running the Hardware and Devices Troubleshooter

The first thing you can do to fix the problem is by running the Hardware Troubleshooter. Although it won’t make much of a difference, there’s still a possibility that it could automatically fix the problem. To use it, refer to these steps:

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

Option 2 – Try to 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 – Run the Memory Diagnostic Tool to check for Memory leaks

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

Note: After you select the option, your PC will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

When you are copying some files from your computer to your hard disk and vice versa or when you have several disks connected to your Windows 10 computer and you suddenly receive an error message saying, “The request failed due to fatal device hardware error”, then this means that there is some issue with the hardware of your computer. This issue might be caused by various reasons but whatever they may be, this post will guide you on how you can fix the “The request failed due to fatal device hardware error”. To fix the error, here are some suggestions that could help.

Option 1 – Check for any hard disk errors

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

Option 2 – Run the CHKDSK utility

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including “The request failed due to fatal device hardware error”.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

• Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer

Option 3 – Verify the hard drive using SMART attributes

In case you don’t know, Windows has a built-in feature of SMART analysis which analyzes the hard drive/SSD and checks all the parameters by performing some minor operations. To use it, follow these steps:

• Tap the Win + S keys and type “command prompt” in the field then right-click on the related search result and select the “Run as administrator” option.
• After opening Command Prompt as admin, type the “wmic disk drive get status” command and hit Enter.
• You should get a result after that, and if you see that it’s “normal”, proceed to the next option below.

Option 4 – Format your hard disk

You can try formatting your drive since this problem also occurs on removable hard drives. In addition, if your drive is not properly initialized, this error will really pop up. Thus, you need to make sure that the hard drive is initialized and that the correct partition style is selected.

• To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
• Next, right-click on the drive and select Format.
• After that, uncheck the “Quick Format” option and then format your drive properly.
• Now once the formatting process is finished, unplug the drive and plug it back in afterward.
• Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
• After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
• From there, right-click on the drive volume and select Initialize Disk.
• Next, select the correct partition type and proceed.

Windows 10 has a pre-installed Weather app that offers the local weather information, forecast, temperature gradient, historical data, multiple locations, and many more. It can be handy especially if you tend to check on the weather. However, if you are one of those users who barely use this app, you have the option to uninstall it from your computer and that’s exactly what we’re going to do in this post. There are several methods to uninstall the Weather app in Windows 10. You can uninstall it via Settings or Start Menu or even using a command in Windows PowerShell. Note that uninstalling the Weather app does not affect the functionality of your Windows 10 computer by any means so you shouldn’t worry about uninstalling it. To get started, follow the instructions provided below.

Option 1 – Uninstall the Weather app through Settings

The first option you can try to uninstall the Weather app is through Settings. It’s a very simple process so you wouldn’t have any trouble following it.

• First, click on the Start menu and go to Settings.
• From there, select System > Apps & Features.
• After that, wait until the list of apps is opened, and then look for the Weather app and click on it.
• Next, click on Uninstall in the given menu to uninstall the Weather app from your computer.

Option 2 – Uninstall the Weather app through the Start Menu

Another simple way to uninstall the Weather app is through the Start Menu. It only takes a right click and there are actually two ways to go about this – one is new with the recent feature update of Windows. How? Refer to these steps:

• Click on the Start button and type in “weather” and right-click on the Weather app which appears in the list.
• Next, click on the Uninstall option. This will uninstall the Weather app.
• You can also use the other uninstall option which you can find on the right side of the list that also shows other quick action for the app.

Option 3 – Uninstall the Weather app through a command in Windows PowerShell

• Tap the Win + X key combination and click on the “Windows PowerShell (Admin)” option to open PowerShell with admin privileges.
• After that, execute the following Remove App package command for the Weather app to uninstall it.

Get-AppxPackage Microsoft.BingWeather | Remove-AppxPackage

• Once done, it will remove the Weather app from your computer.

If you suddenly encounter a Blue Screen error that points out to either the mfewfpk.sys and epfwwfp.sys files, then this post might help. Both of these files are created by third-party software. The mfewfpk.sys file is created by the McAfee security software while the epfwwfp.sys is created by the ESET Antivirus. These files are residual files and sometimes it blocks upgrading Windows 10. Aside from blocking Windows 10 upgrade/update, these files can also cause a Blue Screen error after an upgrade which leaves your Windows 10 computer useless. When you get a Blue Screen error caused by any of these files, you will see an accompanying error message that states, “DRIVER IRQL NOT LESS OR EQUAL”. To fix this Blue Screen error, you can check out the suggestions laid out below but before you do that, you need to create a System Restore point first as it can help you undo any unwanted changes. In addition, make sure to also boot your computer into Safe Mode with Networking before you troubleshoot.

Option 1 – Try to remove the epfwwfp.sys file

You can try to remove the epfwwfp.sys file using Command Prompt. To do so, refer to the following steps:

• Right-click on the Start button and click on Command Prompt (Admin) from the menu to open Command Prompt with admin privileges.
• Next, type the following command and hit Enter to delete the epfwwfp.sys file:

DEL /F /S /Q /A “%systemroot%System32driversepfwwfp.sys”

• After the scan is completed, restart your computer and see if it fixed the Blue Screen error.

Note: You can also use the ESET AV Remover tool to uninstall Eset security software to remove the epfwwfp.sys file.

Option 2 – Try to remove the mfewfpk.sys file

The same with the first option, you can remove the mfewfpk.sys file using CMD.

• First, right-click on the Start button and click on Command Prompt (Admin) from the menu to open Command Prompt with admin privileges.
• After, type the following command and hit Enter to delete the epfwwfp.sys file:

DEL /F /S /Q /A “%systemroot%System32driversmfewfpk.sys”

• Once the scan is completed, restart your computer and see if it fixed the Stop error.

Note: You also have the option to remove the mfewfpk.sys file using McAfee Product Removal tool to uninstall the McAfee security software. All you have to do is download the McAfee Product Removal tool and run it and then follow the onscreen instructions to install it. Once it is installed, click on Next. After you select the radio button to agree to the terms of use, click on Next once again. Finally, restart your computer and check if it is able to resolve the problem or not.

Option 3 – 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. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

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

Option 4 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Blue Screen error. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • 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.

If you suddenly encounter an error message saying, “ File Record Segment is Unreadable ” on a blue screen while booting your PC, it means that your hard drive is in an error state. This particular blue screen of death error might have a lot of bad sectors or might have reached its end. The workarounds you can try to resolve the issue is by locating the bad sectors or checking your hard drive for any discrepancies in the mapping and fix them. Follow the detailed instructions laid out below for these workarounds.

Option 1 – Try to check for any bad sectors and wrong configurations in your hard drive

The first thing you have to check is the boot files on your PC. As you know, your PC boots from these files and if there is anything wrong with any one of them or if one of them ends up getting corrupted, you will most likely see the blue screen of death error or a prompt with an error message saying, “File record segment is unreadable”. According to some users who reported this issue, new hard drives aren’t exempted from this error. That’s why it is recommended that you carry out this solution no matter what kind of scenario you are in. You will have to launch the Command Prompt in recovery mode and see if you can fix the problem by executing the check disk commands.

• Upon booting, restart your PC and tap F11 to go to the recovery environment then select Troubleshoot.
• Next, click Advanced from the given options and select Command Prompt.
• After opening Command Prompt, execute the commands listed below, and don’t forget to hit Enter right after you type in each one of them and if you have installed Windows to some different directory, you must replace “C” with the name of the drive you’ve installed Windows with.
• chkdsk C: /r /x
• chkdsk C: /f

Note: The Chkdsk function might take a while before it finishes its operations so you need to be patient and wait until the entire process is completed. And depending on the situation, it might even take a day at most so patience is really the key here.

Option 2 – Try connecting the hard drive to a different computer

If option 1 didn’t work for you and you’re still seeing the error, you can try connecting the hard drive to a different computer and then copy the data first. Make it a priority to salvage the data just in case the hard drive won’t make it in the future. After replicating your hard drive, you can then try running the chkdsk commands that are listed in option 1 above in the new computer you’re connecting your hard drive to and make sure that you key in the correct drive letter that’s assigned to the hard drive you’re using. After executing the chkdsk commands, plug your hard drive back into the previous computer and then check if you can now boot it without any issues.

Option 4 – Replace the faulty hard drive

If none of the options provided above really worked out then maybe it’s time to consider getting a replacement for your hard drive. In about 50% of the cases about this error, some unfortunate users were left with no choice but to replace the hard drive since the problem is with the hard drive itself. Hard drives have a complex running mechanism which includes a head and the disk that rotates accordingly so you can check if the cables connected to the hard drive are connected properly and if it is in a correct position or not. In addition, you also have to make sure that the SATA adapters where the hard drive is connected are working properly. If the drive is showing problems in the I/O operation, there is little chance for you to use it as a normal hard drive. If the hard drive is in warranty, get it checked and replace it. If not, you might consider taking it to the service center for the specialists to take a look into it.

The docking station was promised upon release of the Deck but it was pushed back and now the official statement is that it is delayed again.

Valve said in an announcement on June 1:

“Due to parts shortages and COVID closures at our manufacturing facilities, the official Steam Deck Docking Station is delayed. We’re working on improving the situation and will share more info when we have it.”

Valve

The docking station was presented at the same time as Deck itself and the whole idea was to make Steam Deck work like a laptop docking station. It has ports for USB devices, displays, and network connections that became functional the moment Deck is placed on it. Docking supports a mouse, keyboard, and external display making it an almost full PC station if needed.

Valve confirmed that its official dock station will not improve performance so while you wait for its release you can use another docking station with a USB Type-C connector.