Windows 10: Large downloads get corrupted in windows 10, whereas smaller ones don't.

I have recently reset my laptop using a flash usb drive to windows 10 Home . I had to do this, because previously my laptop was on windows 11 and suddenly crashed one day, leading to continuous blue screen errors and never booting up. After the reset, i lost all my files but everything seemed to be running fine. Then I noticed that I am unable to download large zip files ~24gb without them getting corrupted. So i downloaded on another pc, and used a pendrive to then extract from the zip file. I still found that some files in the zip were corrupted, although the number of files corrupted wer

:)

 

Dolby advanced audio v2 (Windows 10 don-t work)


Hello guys!I have a problem with advanced audio v2 on windows 10 don-t work

 

Update for Windows 10 is too large to download, needs to be in smaller packages.

I cannot load the Win 10 update because I do not have enough memory. The upload took 4 days over my slow satellite connection and then said it required an additional 4.5 GB. I used the "fix" and cleaned everything there was to clean, but only MBs were
removed (I have only owned this lap top less than 6 months). When I looked at my programs, the total space they use is only 2.5 GB so there simply is not enough hard drive on this Inspirion 14 to run this update program. It suggested I get an additional 10GB
of memory to plug in. Seriously? Is it Microsoft's purpose to limit who can upgrade their products? I suggest Mircrosoft split this download into smaller packages that can be readily uploaded without all the extra steps and frustration.

 

Download Windows 10 TH/RS

*Shadedshun :shadedshu:

Dude, please stop bashing things you don't fully understand.

SFC is the first step, System File Checker. That can fix many issues using various flags and knowing the context, and is a first step when there is doubt about system integrity. This is a simple utility and using SFC /Scannow will be the most commonly used flagged command for initial repair diagnostics. Takes a few minutes and is worth doing to resolve issues. While it can repair many issues, there's also many it cannot. That's where the next step comes in should you need it.

DISM, or Deployment Image Servicing and Management, is the big gorilla in Windows OSes for repairs and image management. It has a wide variety of uses from image capture and deploy to repair.

The common command for DISM was DISM /Online /Cleanup-Image /RestoreHealth,

Just running this can result in a system being repaired, but since the launch of Windows 10, the image check has become more complicated, requiring you have the Install.WIM file available for the OS version you're trying to repair. This is relatively, though with Microsoft's deployment of Windows 10, most ISO's you get from them have an Install.ESD that must be converted to a .WIM file. Pretty easy to do with a command in CLI or Powershell.

I typed up an article about this in the past...I'll go ahead and share it here for a series of steps a person could take to repair OS corruptions in Windows 8, 8.1 and 10. It's not hard to do, but takes some attention to detail, being able to handle command line (which is easy), and a little patience.

I've personally fixed/repaired dozens if not hundreds of systems with these utilities, because simply... THEY WORK. How do I know? Because I'm a systems and network professional that has to manage 100s of Windows PCs ranging from XP to 10, and where we can use these utilities to repair corruption, we save a ton of time. My technicians, bench guys and engineers all know and use the hell out of these utilities.

I find it hard to accept your statement above as something acceptable to even say here, it clearly shows your lack of experience with using the repair utilities SFC and DISM correctly or looking into what the failures were and how to fix them appropriately. Nor is that kind of crap even what TPU is or has ever really been about, and being such a long time member I would have expected you know that...though you've always been that way so maybe it's just habitual...surely not helpful to anyone else participating in this thread, or even yourself.

The OS is literally telling you what is wrong and where it's keeping the information so you can look into it further, that's not whining, that's stating facts. Nice try though. If you don't want to learn how to fix OS corruption, don't blame the OS or tools, blame yourself and shut up about it, and don't bitch about the OS utilities whining...LOL, because in reality wouldn't your bitching mean you're whining??? *Slap :slap:

So knock that shit off and let's fix the issues instead k? *Wink