Office 2021 release date set for October 5th

If you encounter a Blue Screen error that points out to the CMUDA.sys, read on as this post will guide you in fixing it. The CMUDA.sys file is a Windows operating system driver file that is related to the USB Device Audio capabilities of a computer. There are times when this file causes Blue Screen error due to some conflicts in RAM or some incompatible firmware or hard disk issues, corrupted drivers or malware infection, and so on. There are various Blue Screen errors that are related to the CMUDA.sys file such as:

• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN A NONPAGED AREA
• IRQL NOT LESS OR EQUAL
• SYSTEM THREAD EXCEPTION NOT HANDLED (CMUSBDAC.sys)

In most cases, the CMUDA.sys file usually triggers the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Blue Screen error. Although this Blue Screen error may seem complicated, its workarounds are straightforward so you won’t have any problems in following them.

Option 1 – 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.
• After opening the Device Manager, locate the device drivers that are marked with a small yellow exclamation mark icon and right-click on each one to open their Properties. On the other hand, you can also look for sub-entries under Sound, video, and game controllers like the C-Media USB Audio Class
• 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. You can download the as C-Media USB Audio Class driver from the cmedia.com website.

Option 2 – Try to recreate the CMUDA.sys file

The first thing you can try is to recreate the CMUDA.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. Which 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 CMUDA.old.

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

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

Option 3 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter 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.
• After that, 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.

On the other hand, you can also try running the online Windows 10 Blue Screen troubleshooter from Microsoft. It is a wizard that could help you fix any Stop errors related to the CMUDA.sys file and will offer you helpful links as you use it.

Option 4 – Try running the DISM tool

You can try running the Deployment Imaging and Servicing Management or DISM tool to fix the Wdf01000.sys 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.

Option 5 – Run System Restore

Running System Restore might also help in fixing Blue Screen errors related to the CMUDA.sys file.

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

The author of the famous software library mode-ipc that gets over a million downloads per week found that it has some questionable code inside. The code itself behaves like this: if it finds out that your location is within Russia or Belarus it will try to replace the contents of all files on the computer with a heart emoji.

One important thing is that we here are not supporting the current Ukrainian situation and are against any type of violence or war but we also do not support this kind of behavior as well. If we look at this only from a technical perspective, we would then classify the mode-ipc library as malware and a harmful piece of code no matter the motivation behind it.

So this so-called protestware is well basically malware, but not always, it will protest when certain conditions are met. The issue with this is that companies and users should not be placed under harm if they do not share the personal view of the code author. Imagine if, for example, I would publish code to delete all pictures from your computer if my code found out that you do not like metal music. I guess you not liking metal music and war in Ukraine are two very different things but the source is the same, unreliable code that invades your privacy in order to serve one purpose, punishment for disagreeing with my personal views and that should not be allowed.

Not all protestware are equal, some will not harm your computer on purpose, they will just annoy you with some messages like viruses did in their infancy stages, others might place some developer sanctions but no matter the outcome basic principle is the same, it does something without user consent and without informing the user that something like that might happen.

On the internet, many blog posts and discussions were open about this issue and its morality. Discussion is still active with different takes on the situation and how to prevent it. Our take on this matter is that professional developers should have standards and not submit to doing harm for the sake of personal views and feelings.

In the long run, this kind of behavior and practice can only harm developers involved in this kind of entanglement. Infected libraries will in time stop being used since people would not trust them and authors will have a stain on their name as impulsive or not trustworthy.

DLL files, also known as Dynamic Link Libraries are external parts of applications that run on Windows as well as other operating systems. Almost all applications are not complete in themselves and store code in different files. In this post, we will be discussing one DLL file called ntdll.dll. It is described as “NT Layer DLL” which means that it contains some Kernel functions that help in the normal functioning of the Windows operating system. It is created by Windows in the System32 folder when the OS gets installed. This file can serve different programs simultaneously by providing them with different Kernel functions which support the programs’ performance. However, if you encounter the ntdll.dll file error on your Windows 10 computer, read on as this post will guide you in fixing the problem.

Option 1 – Try to re-register the ntdll.dll file

You may have to re-register the ntdll.dll file using the regsvr32.exe before you can successfully install the program and fix ntdll.dll file crash error. The Regsvr32 tool is a command-line utility that can be used to register and un-register the OLE controls like DLL and ActiveX (OCX) control 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 /u ntdll.dll
  • exe ntdll.dll
• 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 2 – Disable problematic Internet Explorer add-ons

There are instances when some add-ons in the Internet Explorer browser can cause the ntdll.dll file crash error. Thus, you need to disable some add-ons in Internet Explorer and then check if it fixes the problem.

Option 3 – Try running the DISM tool

You might want to repair potentially corrupted files in your system as having them could also trigger the ntdll.dll file crash 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 DCOM error is now fixed.

Option 4 – Try to run the Program Compatibility Troubleshooter

You might also want to run the Program Compatibility Troubleshooter. This built-in troubleshooter is available in the Windows Update & Security section. From there, select Troubleshoot. This will find a list of programs for you and since you have already downloaded the driver files, just click on Not Listed located at the top of the program list. After that, browse and select the driver files and then let the program do its job.

Option 5 – Try to replace the DLL file with 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:WindowsSystem32
  • x64: This PC > C:WindowsSysWOW64
• 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 6 – Try scanning your computer using Windows Defender

The ntdll.dll file crash error might also be infected with malware or virus and to eliminate it, 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.

Error Code 8024402C – What is it?

When upgrading to Microsoft Windows 10, some users may encounter Error Code 8024402C. This error, while attempting to update, is a result of five possible issues. The error code itself is not a critical concern, yet while the error is occurring, users will not be able to upgrade their Windows software. As with any Microsoft error code, even if it is not critical, it is recommended that the error be addressed sooner rather than later. An insignificant error now could lead to a larger, more catastrophic error later on. Common symptoms include:

• A dialog box appears with the Error Code 8024402C when attempting to upgrade to Microsoft Windows 10.
• Your current version of Windows is unable to recognize the need for an update to Microsoft Windows 10.

Solution

Error Causes

As previously stated, there are five major reasons why error code 8024402C occurs.

• An erroneous character in the proxy override settings
• A wrongly configured firewall is preventing the update from taking place.
• Attempting to access the Windows 10 update through a VPN (Virtual Private Network) connection.
• Workstations that operate behind a corporate ISA server.
• A corporate network system that does not have auto proxy enabled.

The sooner these known causes are addressed, the sooner you will be able to successfully upgrade to Microsoft Windows 10.

Further Information and Manual Repair

Microsoft Support posits four different resolutions to these known error code 8024402C issues. Some of these methods will be more comfortable for at-home users than others. If you are experiencing this issue in a corporate or business setting, it may be better to have your IT tech or department attempt the methods.

Method 1:  When your firewall is causing the issue.

1. Access your firewall software.
2. Specifically, look into the settings associated with your firewall.
3. Make sure that the following three websites are listed as exceptions to your firewall or proxy.

• https://*.windowsupdate.microsoft.com
• http://download.windowsupdate.com
• http://*.windowsupdate.microsoft.com

4. If any of these websites are missing from your firewall list, add them to the list.
5. Restart your Microsoft Windows 10 update.

Method 2: For an erroneous character in the proxy override settings.

1. Open internet explorer, if you use another program to access the internet, you will still need to use internet explorer for this solution.
2. Open your internet explorer tools window.
3. Click on internet options.
4. Choose the connections tab.
5. Select LAN settings.
6. Choose the Advanced option.
7. Delete anything that appears in the exceptions section.
8. Closeout of internet explorer.
9. Click on your start button.
10. Select RUN and type CMD into the field, press ENTER.
11. This will access the command prompt screen. Type “proxycfg -d” and press ENTER.
12. Type the command “net stop wuauserv” and press ENTER.
13. Finally, type “net start wuauserv” and press ENTER.
14. Now you have cleared your proxy cache. Access the Microsoft Windows 10 update again to download.

Method 3: If a VPN connection is causing error code 8024402C.

1. Disconnect from your VPN connection, thus connecting directly to the internet without a proxy or network.
2. Retry the Microsoft Windows 10 update.
3. After the update is successful, reconnect to the VPN network.

Method 4: Use this is an ISA server is in place at your networked business site.

1. Access the ISA firewall client option. From here your goal is to initiate the ISA server automatic detection feature.
2. From the control panel, select the firewall client option.
3. Choose the configure option.
4. Check the box next to “automatically detect firewall server”.
5. Select the “update now” button.
6. Click the OK button.
7. Restart your Microsoft Windows 10 update.

Again, not all of these methods are meant for computer users who do not usually explore and change software settings of this nature. If you do not feel comfortable with any of these methods, you can opt to download and install a powerful automated tool to repair Windows error code 8024402C.

If you encounter an error saying, “Boot Device Not Found” when you turn on your Windows 10 computer, then you’ve come to the right place as this post will guide you on how you can fix this problem. Apart from the error message, you will also see a message that states, “Please install an operating system on your hard disk, Hard Disk<xxx>”. You will then be asked to tap the F2 key to initiate the System Diagnostics. If you install the Windows operating system, it becomes the boot device, and when your computer boots, the UEFI or the BIOS looks for the operating installed on your drive and continues the process. So when you encounter the “Boot Device Not Found” error, this means that the UEFI or the BIOS wasn’t able to locate the drive where it can boot. There are several suggestions you can check out to resolve this error. You can try checking the connection with your boot drive or change the boot order. You can also fix the Boot Record from Recovery and see if the primary partition is active or not. But before you troubleshoot the problem, make sure that you have a bootable Windows USB drive ready since two of the options provided below will require you to boot into the Advanced Recovery mode. Once you have this covered, proceed to each one of the following options.

Option 1 – Try checking the connection with the boot drive

If you have a custom computer that comes with a cabinet, you might want to open it and remove any connected power supply, and then check the wires. As you know, drives are connected with the motherboard using a cable. So all you have to do is check if both ends are connected properly and make sure that the connection is not loose. You could also try to unplug the cable and plug it back in.

Option 2 – Try changing the boot order

You might also want to try changing the boot order of your computer. Each time a computer boots, the BIOS or the UEFI follows a boot order. It is the one that tells where to first look for the boot drive and if for some reason, a USB is connected to your computer and the first boot device found in the USB, then you have resolved the problem. All you have to do is to remove the USB device and boot or go into the BIOS and change the boot order yourself.

Option 3 – Try to rebuild the BCD files

The next thing you can do to resolve the issue is to Rebuild Boot Configuration Data or BCD files.

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /ScanOS
  • bootrec /RebuildBcd

• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed the “Boot Device Not Found” error.

Option 4 – Try setting the System Partition to Active

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

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

diskpart

• Now type the following command:

list disk

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

select disk number

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

list partition

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

select partition number

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

active

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

Once it’s done, the primary drive should now be active and you should now be able to boot into your computer without the “Boot Device Not Found” error.

If you find that your headphones are suddenly not working, read on as this post will help you sort out the problem. There could be several reasons why your headphone is malfunctioning, it could be due to an update you just installed, or it could also be due to incompatible operating system, drivers, and so on. Although updates are created to fix bugs on a computer, there are times when it also causes some issues in the computer. One of the issues it causes is the broken headphone. When this happens, the computer will stop playing any audio using the headphones. The problem, as pointed out, could be due to Windows Updates or incompatible or corrupted drivers in the system. To resolve this problem with the headphones, there are several fixes you can check out. Make sure that you follow each one of the given potential fixes below.

Option 1 – Try to set the headphone as the default device manually

There are times when you plug a headphone, it does not toggle the default audio device. Thus, to fix this issue, you have to set the default audio device to the headphones manually. To do that, follow these steps:

• First, right-click on the volume icon located on the system tray.
• Next, select the Open sound settings option to open the Sound section in the Windows 10 Settings app.
• After that, go to the Output section and select Headphones for the “Choose your output device” option. This should fix the problem for you.

Option 2 – Try to update, rollback or reinstall the Audio driver

If the glitch in your audio has something to do with software, chances are it might be related to the audio driver – it could be that the newest version of your Windows 10 does not work well with the old version of the driver. This is why you have to update your audio driver to the newest available version.

• Tap the Win + R keys to open the Run dialog box and then type in MSC and tap Enter or click OK to open the Device Manager.
• Expand the section for the outdated device drivers.
• And then select the outdated driver(s) and right-click on it/them.
• From the drop-down menu, select the Update Driver option and follow the on-screen instructions to install the latest version of the driver.
• Then also click on the option, “Search automatically for updated driver software.
• Restart your PC after the installation.

Note: If updating the Audio driver didn’t work, you can go to the website of your PC manufacturer and look for the support section where you can download the drivers for your computer. You just need to take note of your PC’s correct model and model number so you can find the appropriate driver.

Option 3 – Try checking the status of the audio-related Windows Services

The Windows Services manages audio for all Windows-based programs and if this service is stopped, audio devices, as well as effects, will also be affected and if this service is disabled, any services that depend on it explicitly will fail to start. So you need to check the status of this service. How? Follow the steps below.

• Tap the Win + R to open the Run dialog box.
• Then type in “MSC” in the field and tap enter to open the Windows Service Manager.
• Next, navigate down to the Windows Audio Service and double-click on it to open Properties.
• After that, set the Startup Type to Automatic and then click on the Start button and if it has already started, stop it and then start it again.

Note: You should also make sure that the following Dependency Services are started and have Automatic Startup type:

1. Remote Procedure Call
2. Windows Audio Endpoint Builder

You should also start the Multimedia Class Scheduler and set it on Automatic if you have it in your system. The Multimedia Class Scheduler Service or MMCSS is a service in Windows that allows multimedia applications to get prioritized access to CPU for time-sensitive processing like the multimedia applications as well as prioritized disc access to make sure that the process does not lack data to process.

Option 4 – Try running the Playing Audio Troubleshooter

Since the Windows 10 operating system has the Playing Audio Troubleshooter, you can use this troubleshooter to try and fix the problem with the headphones. You can access this tool in the Control Panel or in the Taskbar Search and even on the Troubleshooters page of Windows 10. Run this troubleshooter and see if it can fix the issue or not.

Option 5– Try to rollback or install a newer Windows Update

As mentioned earlier, the issue with the headphones could be due to a Windows Update. Thus, to fix the problem, you can try to either roll back or install a newer Windows Update.

Cyclic Redundancy Check Error - What is it?

To begin with, Cyclic Redundancy Check is basically an error checking technique. This technique is used for data verification. It detects accidental changes in the data. It is used by computers to specifically check the data stored in the hard drive or optical disks (DVD’s and CD’s). The Cyclic Redundancy Check error occurs when the data being verified on the hard drive or optical disks is corrupt. Symptoms for this error code include program lock-ups, slow PC performance, inability to run and execute the desired program, system freeze and shutdown and startup issues.

Error Causes

The Cyclic Redundancy Check error code occurs due to the following reasons:

• Cluttered hard disk
• Registry corruption
• Misconfigured files
• Unsuccessful program installation

All these causes points towards registry issues and poor PC maintenance. The registry is the main database of the computer. This part of the PC saves practically every activity you perform on it including activities like application installation and deletion and web browsing to name a few. With time and frequent PC usage, the files generated from every activity you execute on your system begin to load the registry. These include even the unnecessary files like junk files, internet files and files of applications that you’ve uninstalled. All these files overload the registry and acquire a lot of hard disk space. And when you don’t remove these files on your system, eventually it leads to file misconfiguration, cluttered disk, and registry corruption. New program versions that you want to install and run on your system also don’t function because the files of the old program version still saved in the registry.

Further Information and Manual Repair

As the Cyclic Redundancy Check Error causes data corruption on the hard disk, it is advisable to fix this error right away. The reason is that it can have serious consequences. It can lead to data loss, fatal crashes, and system failures. When it comes to resolving Cyclic Redundancy Check Error, there are two ways to fix it:

Run the CHKDSK application.

This is a built-in feature in your Windows system. It checks for hard disk damage and attempts to resolve it.

MSI.chm error is a common Windows Error code that occurs when the Windows OS becomes overloaded with invalid system references.

Solution

Error Causes

The MSI.chm error is normally triggered by the following causes:

• Poor PC maintenance

You may experience the MSI.chm error if you don’t pay attention to its maintenance. This usually happens when you don’t run antivirus software or update programs and drivers frequently.

• Registry files get corrupt and damaged

This error may also occur when the registry files of your PC get corrupt and damaged. This normally happens due to continuous writing, editing and deleting of information from your PCs registry over time as programs are installed, modified and deleted. Other causes include: malware and system conflicts.

Further Information and Manual Repair

When you come across the MSI.chm error on your PC, it is advisable to repair it immediately without any delays. If you procrastinate in repairing this error, your PC is likely to be exposed to risks like:

• Slow PC performance
• System failure and crashes

Nonetheless, to resolve this error you don’t have to get the assistance of an IT professional. The MSI.chm is easy to repair and you can resolve it in no time even if you aren’t technically adept. Here are some of the best ways to repair the MSI.chm error on your PC successfully in the shortest time:-

Cause: Corrupt and Damaged Registry Files

Quick Fix: If you think the MSI.chm Windows error on your system is related to Windows registry issues, then the best way to resolve this error is to download and install a Registry cleaner tool.  A word of advice here is to always download such tools from a reliable and a trusted website. Once you download the Restoro, run it on your PC to scan for errors. The scanning will usually take a couple of minutes. So, it is advisable to be patient. After the scanning is complete, you will see a detailed scanning report highlighting the registry errors on your PC. Now to resolve the MSI.chm error that has occurred on your PC due to registry issues, click on the ‘Repair’ button to fix the error. Once the repairing process is complete, restart your PC. Restoro helps you not only fix the MSI.chm error but it also helps improve the speed of your PC, and protects it from failure and crashes.

Cause: Poor PC Maintenance

Quick Fix: If the cause of the MSI.chm error is poor PC maintenance, then the best way to resolve the error is to update the drivers. You can do this by installing the latest drivers for the devices that you think are now old and need to be updated. Here’s what you need to do: First find which devices don’t have drivers installed. For this go to the start menu and then click on the Control Panel. Now open the Device Manager. The Device Manager will list down all the devices that don’t have drivers installed with yellow exclamation point icons next to the device name. As for the updates, the general rule of thumb if the driver does not support the program you are trying to run, then this means that you probably need to update the driver to ensure compatibility. For example your video card driver does not support a newly launched game, then you definitely need a driver update to play the game on your PC. To install or update drivers on your PC, you can either get CDs from the market or you can download updated versions of the drivers from the main manufacturer’s website for free. You can also use automated solution for all of your driver issues: So, next time when you or your friends encounter this problem, try these quick fixes to repair the error without any hassle.

When performing a Windows Backup to the NAS device (backup to a network share) that is running Samba, fails with an error message The backup failed, The version does not support this version of the file format (0xC03A0005). The problem occurs because of a conflict with the VHD file that is created by Windows Backup and is mounted during the process. There are three types of VHD files:

1. Fixed,
2. Expandable
3. Differencing

If the VHD file is a sparse file that is not supported by the native VHD driver, the mounting will fail, and you will get this error. An example VHD file is one that keeps expanding depending on the backup size. The problem occurs only in the case of  File Level backup (file/folders in a volume) but not on the block level backup as the vhd file is never mounted. However, in the case of File Level Backup, the vhd is mounted, created by Windows Backup, which does not support the mounting of sparse files.

The solution is to use Strict Allocate: option in the smb.conf file

Login to SMB using SSH. Open the configuration file using the VI editor located at /etc/samba/smb.conf. If the option is not there, you can manually add strict allocate = yes which will make sure there are no sparse file that is created.

Microsoft wants to escalate the situation from Australia to the EU, what a surprise. Hello all and welcome to another news article, this time we are focusing on Microsoft pushing the EU to accept law proposition from Australia. For all of you who are not familiar with the given situation let me quickly explain. The feud began when the Australian government proposed a new law that targeted Facebook and Google specifically. The government said that it believed that both of the tech giants were using content from news outlets without paying. Have you ever seen the little news snippets that Google or Facebook sometimes show its users to keep them up to date? These are lifted directly from news websites, and the Australian government claimed that this practice meant that people didn't bother visiting the news website. This then staved news websites of revenue. As such, the government put forward a new law that would mean Google and Facebook would have to pay the source website for every time they displayed a news snippet. Facebook responded by removing its Australian news coverage in light of the law. Google, however, put up a fight. It argued that its snippets encouraged people to click on it to read more, thus driving more traffic to the news website. It also said that such a law would be too expensive to maintain in the long run. As such, Google threatened to remove itself from Australia if the law passed. This was likely a scare tactic, as 95 percent of Australian web users use Google; however, it actually opened the door for its rival, Microsoft. Microsoft saw how it could push its own search engine BING to replace google. It of course went and reached the Australian government to assure them that BING is more than capable to fulfill its needs and fully abide by the proposed law. Now Microsoft knows that if this law passes it could see a similar situation happening in Europe and it is pushing it. US News reported on how Microsoft plans to encourage EU countries to adopt this new law too. The company has teamed up with the European Publishers Council and News Media Europe to make the following statement: Publishers might not have the economic strength to negotiate fair and balanced agreements with these gatekeeper tech companies, who might otherwise threaten to walk away from negotiations or exit markets entirely