Cannon install new patch

protoss2004

Hello

I've tried several times to update to the new patch.

The launcher downloads the data and when tries to apply the patch , it gets stuck at the same point
(30265.42mb remaining if that helps a bit )

Some notes.
While applying the patch , the disk usage of the launcher in task manager seems high but normal (I/O) 250mb/sec | disk usage 50-75%

When reaching the point that the problem appears , the I/O drops to 0% , but the disk usage skyrockets to 100% , and the computer stutters a lot ( new windows take 3-4 seconds to open etc ) and when I kill the launcher from task manager , the pc goes back to normal.

Tried to disable my antivirus , didn't fix the problem.


Any ideas how to solve this ?

Thank you.

ValeofAryan

I ran into the same problem.

The patch gets stuck at 38% and it won't go any further.

I made a post on it as well but no replies on how to fix it.

If you figure anything out post an update.

Thanks!

protoss2004

Just to add that I tried doing a repair , but without success.

The repair procedure halts , the same way the update do.

When reaching a particular point, disk active time reaches 100% and I have to kill the launcher in order to make the pc responsive again.

Some more info regarding hardware :
Hard disk is Samsung SSD 860 EVO 500GB
and OS is Windows 10

protoss2004

I've managed to find a solution.

It seemed for some reason , the SSD must had some bad sectors.

I discovered it out by looking the Windows Event Viewer and seeing some
The device, \Device\Harddisk0\DR0, has a bad block errors.

I run a checkdisk with fix , and then the game installation completed successfully.

If you have the same reports in your event viewer log, try doing a checkdisk
by opening command promt (cmd) and running a checkdisk with fix option

chkdsk /f

--- WARNING ---
Checkdisk sometimes can lead to weird behaviors and even ruin your data.
I recommend doing a full backup before trying it.

Hope this helps

ZOS_Bill

Thank you for the update. We are glad to hear you found a solution related to your SSD. With the issue resolved, we will now close the discussion.