Even with the new Groove Music in Windows 10, a lot of users still prefer to use the old Windows Media Player. This isn’t surprising since Windows Media Player still remains to be one of the best players you can find. However, that does not mean that it is without flaws as it could still encounter some issues from time to time.
One of the issues you might encounter when using the Windows Media Player is when you try to burn DVDs or CDs but end up failing due to an error that pops up that says, Windows Media Player cannot detect the length of the file. At the time of writing, it isn’t clear yet what the real cause of the error is. However, there are several fixes that are provided in this post for you to check out so you can resolve the problem. You can try to get rid of any unsupported files from the burning list or you could also try running the Windows Media Player troubleshooters. Aside from that, you could also try to drag and drop music or change the burning speed. For more details, refer to the following options.
You must get rid of the unsupported files from the list of files to burn. This list can be found on the right-hand side of the Windows Media Player. One of the indications that a file is causing problems is when there is a white cross in a red circle next to the file. You can simply click on that icon to remove the file from the burning list. Once you’ve gotten rid of all the unsupported files, try to burn your files to the CD or disk once more.
The next thing you can do to fix the error is to run the built-in troubleshooters for the Windows Media Player. Windows 10 actually comes pre-packed with three troubleshooters designed for Windows Media Player. They can help in fixing the “Windows Media Player cannot detect the length of the file” error. To run these troubleshooters, simply tap the Win + R keys to open the Run dialog box and type “msdt.exe -id WindowsMediaPlayerConfigurationDiagnostic” for the Windows Media Player Settings troubleshooter or type “msdt.exe -id WindowsMediaPlayerLibraryDiagnostic” for the Windows Media Player Library troubleshooter, or type “msdt.exe -id WindowsMediaPlayerDVDDiagnostic” for the Windows Media Player DVD troubleshooter.
Another thing you can check out is to drag and drop all the tracks into the Windows Media Player before you burn them. All you have to do is open the folder where the tracks are located and highlight all of them and then drag them to the Windows Media Player. It should now be able to detect the length of each one of the tracks without any errors.
Since the burning speed is set to fastest by default, you can try to change the burning speed to resolve the problem. Just open the Options window and then go to the Burn tab. From there, select either Medium or Slow burning speed and save the changes made. Now try to burn your files to the CD or disk once again.

Hardware under the hood
Error Causes
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.
Error CausesSTOP: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000)
Error Causes
If you are one of the mentioned users and for any reason, you do not wish to have a touchscreen-enabled then sit back and relax, we have you covered in this tutorial on how to fully disable touchscreen inside Windows 11.