As an IT tech in the past, I used to use the prospect of reloading Windows as a pain point for my regular users who professionally destroyed their machines over and over. " Sorry, but looks like we're gonna have to start over...again" serves as a great learning experience for people who refuse to listen to your directions over and over on how to keep their machines running smoothly. With that being said, I eventually would allow to them that there is a way to repair windows fairly reliably after they had their collective heart attacks at the prospect of losing their data , but say " DONT DO THAT AGAIN!" . At any rate, I am glad DISM and SFC work like theyre supposed to.
Customers that regularly trash their systems is just more money for me. I don't mind fixing the same or similar problem over and over again. If a customer doesn't listen they just have to pay me again to fix it. It all pays the same, doesn't bother me at all.
Your content is great! Every video should be like this, straight up, no unnecessary explanation, and short videos about complicated things, and well explained tutorial. This is the best tech channel ever. Earned a sub, Rich!
You have right, but i like when explanation is coming but not like some professionnal explain like complicate for show that are very clever and some peopel they repeat just for repeat and they do not know what to do and what they said too, copying, that why i prefer too explaination for see if peopel are truth or not or says a sheet !! iam agrre with for 50 %
Excellent! I've made your tutorials required viewing for our techs. I'm fed up with hiring computer science graduates that only know how to code in various languages but know shit when it comes to repairing Windows. The academic curriculum is severely lacking.
See, this is the stuff I have a hard time finding when you need to actually fix a broken Windows installation. Thank you very much! Just replace the bad ones from an image, plain and simple video.
you are such a life saver!!! ran into this problem on my grandmothers computer i built for her. had a recent windows update fail and corrupted it soooo bad it wouldnt boot and starup repair just laughed at it. i knew how to run it on a local machine but couldnt find the information on how to run it from a recovery usb in a clear concise way. awesome job
I want to thank you for these videos! I am CompTIA A+ certified, and there is ZERO reference to this valuable info! You da man! oh, and a company i worked for had a policy of reimaging drives rather than troubleshooting the computer.... must not have seen your videos! lol
Suggestion for a future video in the series: Things you should do BEFORE windows breaks to make it easier to revover. Turning registry backup back on ( See ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-eY76UVXxENo.html ) of course, but should I use the windows scan disk tool in properties? Should I optimize my SSDs? Create a recovery point? Anything special I should back up to a USB drive to make recovery easier?
Thanks for your videos. I did the reinstall windows many times. I'm downloading some of your videos onto my tablet so I can see watch the instruction incase I need it as there is no way I would remember them.
Instead of reloading Windows, I just built a new machine. I had the parts laying around and was due for an upgrade anyway. I'll try giving this a shot since I didn't nuke my old rig's drives. Maybe this'll stop my old "nuke it" habits. Thanks for the knowledge!
Great in depth tutorial !! Just one question - does it work if the files on the USB are newer than the offline drive? So for example the unbootable system has Winbdows 21H2 but the downloaded ISO is windows 22H2 ?
Thanks for this video and the last one also. Have noted down all the command. In the future when I have a Windows that fails to boot, I can "try" to fix it. Recently, I migrated a Windows 7 on a Asrock Z68 Pro3 with RAID1 configuration (one drive hardware failing) to a non-RAID SSD drive using MiniTool Partition Wizard - Migrate OS to SSD. That ended with error BlInitializeLibrary failed 0xc0000001 at boot. After many hours of trial and error, I was able to fix it with DISM++ (found on Sergei Strelec Boot CD/USB) - Toolkit - Bootmgr repair. Thereafter upgraded to Windows 10.
Mate this works just pay attention to detail. You probably didn't locate the right drive letter for the windows partition. Just go through the alphabet if you must 😮😅. Also make sure your recovery drive is an original windows iso matching the same build and version installed on your windows os drive. THIS IS IMPORTANT!!. lastly make sure the recovery drive isn't a reconstructed one as that will definitely differ from the process guide shown in this tutorial. Anyway thank you so much, after all day trying to find some information that I needed to clarify in case of completely destroying hours of back and forth installation, trial and errors but really and desperately trying so hard avoiding a long and painful stare down at a status bar barely moving whilst chucking down a jar of coffee. At the end of the day what was I thinking hey? As if they're are shortcuts for this sort of process. Believe me I should know, I've just done them all lol. Hence why I'm here expressing my deepest gratitude and also highest level of frustration. Anyway cheers mate.
Correction: this worked for you. Just because it solved your problem doesn't mean it will solve everyone else's or that their error is from not following properly. That just shows your own ignorance in thinking this is a one size fits all without the ability to actually inspect and see if another person's issues are due to another problem or their own failure to follow the steps.
I came across your videos a couple of weeks ago. I took your tips on how to deal with the 100% Disk problem and they worked great. I'm interested in using the two tools you mentioned in part one of this series. My question is: will those tools work effectively if the window search service is disabled? I disabled that service to lower my disk usage? I subscribed and I am still reviewing your older videos for helpful tips. You do a great job making these things seem simple which I know are not that simple.
I'm here because Windows 11 screwed up after an update restart. It's a shame that Microsoft does such a terrible job with its updates that its customers have to be terrified every time they get notifications to restart to install updates.
@@aya.el1001 No, still an issue. I have done two subsequent update installations and my screen goes into a perpetual flashing state after the update - unusable. Then I had to uninstall the update only to have Windows bug me with a new message that my computer needs an update. So frustrating.
I swear! Those updates are such a mess and whatever how many times you reschedule it to not do the updates one day u will find out the system did it by itself and then start the problems 💀…
Thanks for the videos!! I think it would help if you started the video with a screenshot of the error message as to why it won't boot so you know which repair to try.
SFC fixes a lot of problems with Windows. It's not just fixing one specific error message. SFC should be at least tried with all error messages. The tool scans Windows system files for corrupt files and replaces them with good ones if it finds any that have been corrupted.
I rarely comment but took this extra step to say this is a very useful video very nicely explained that helped solve my windows issue which wasn't booting, I am extremely thrilled and thankful and appreciate the knowledge sharing!
Hi, great video I've used these tools before from others descriptions, but you explain it all way clearer. Unfortunately no bueno for me... I have the same windows version, exactly the same dism version and all I get in dism is "error 87: the cleanup-image option is unknown". Sfc gives me: Windows Resource Protection could not start the repair service. Can I do anything else to save this Windows 10?
Hey so far its a great video but for some reason I don't see that Install.esd file or install.win , I do see at the very bottom a files called install.swm and it's basically the biggest file in the sources folder. Could this maybe be it?
My system won’t boot and I ran the original dsm command without needing the scratch directory. The scan worked and recovery was successful. But my system still won’t boot into windows
Very useful! Thank for the effort. The $64 question for me and the one I couldn't solve for almost a year and I hope you ir someone here has the knowledge regarding that. The problem is my recovery cannot see any of my drives at all. Though Windows is running flawlessly. I do regular updates when they don't have problems. The system is 4 years old the hardware is almost one year old . 13 Gen CPU with Z690 MB. This is driving me crazy lol. If i took my NVMe and plugged it in my nephew's PC (6600x CPU and b560 MB), the recovery works perfectly. One more thing is that I have to make my recovery drive visible otherwise I cannot even go to recovery environment which is weird.
Just got it fixed few days ago, It turned out you have to disable Intel Rapid Storage Technology in BIOS. Then recovery environment will see all your drives
Hi again, what I forgot to mention was the shortcuts that I spent so long to remember. And after a couple hours from posting a comment on here. I remembered. I got it and it takes less than 5mins to execute. But system restore points from an earlier date or time prior to the non-bootable Windows 10 OS. Is a must if you want to resolve this problem via system restore point. If anyone wants it. Let me know. Thank you
This issue occurs because Microsoft's 'install.esd' file comes packaged with multiple versions of Windows (Home, Pro, etc.). When using the DISM command in the video, DISM fails as a result. It worked in the video because as he states @ 3:52 "I'm not gonna do that because I've already created one for myself." It seems he created a Windows install USB in a different manner from in the video or he created one a long time ago before Microsoft started bundling multiple versions within a single .esd file. We can fix this problem with a couple extra commands. For this entire demonstration, assume your Windows boot drive is C:, your Windows install USB is D:, and your scratch directory is 'C:\Temp'. Make sure to make modifications to any of these following commands if you're using alternate paths. First we need to extract the correct Windows image from the 'install.esd' file. Type the following command into CMD: DISM /Get-WimInfo /WimFile:D:\install.esd This command will output the 'index' values for each version of Windows within the 'install.esd' file. Make note of the index value that correlates to your Windows version. As of the Windows 10 22H2 MCT .exe, Windows 10 Home is index 1 and Windows 10 Pro is index 6. For the rest of the demonstration, let's assume you're using Windows 10 Home so we shall use index 1. Now that we have the index value of the Windows version we need, let's extract it. We can extract it to the flash drive or the boot drive. For this demonstration, let's extract to the boot drive. DISM /Export-Image /SourceImageFile:D:\sources\install.esd /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:Max /CheckIntegrity This extracts the Windows 10 Home image file to the root of the boot drive (C:) as a '.wim' file. The '/SourceIndex:1' switch specifies the index for the Windows version, '1' is the index for Windows 10 Home; if you're not using Home (Pro, etc.) then change '1' in this switch to the correct index value that we retrieved earlier. The '/Compress:Max' switch compresses the '.wim' file to use less space but will take longer to do; if you don't mind using more space, you can use '/Compress:Fast' or '/Compress:None'. Now we can actually fix the issue! DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:C:\install.wim /ScratchDir:C:\Temp If you still get the error, check your syntax carefully and attempt the above command one more time (Hint: press the 'Up' arrow key on your keyboard to retrieve the last executed command). If you still get the error even after checking your syntax and trying again, attempt to re-export the 'install.esd' file using the '/Export-Image' command but this time use 'Compress:None'; this will take up far more space but may fix any compression/decompression errors that may have occurred. This works for Windows 11 too! Hope this helps!
Never had to do this at all on Windows 7 and 8/8.1 as those OSes were super reliable and rarely needed repair but Windows 10 is a completely different story, in corporate environments we just wipe and load if the OS usually Windows 10 is corrupted. Alternatively the windows install USB does have another option called Refresh this PC which is less time consuming and does the same thing.
Hi I've been having these issues on 2 computers i tried everything you've pointed out. I Had no issues going step by step but when i restart computer still doesn't boot into windows??? Ive tried everything and nothing seems to help i just get the recovery screen loop. What am i doing wrong?
Wish you had this up earlier lol but fortunately I had a full clone backup of my laptop so was able to restore my laptop from that once I remember I had it... 4hrs later lol ugh...
god damnit! i could´ve used this 2 or 3 years ago i think...some day i just absolutely couldnt get into my windows installation anymore....my brother is pretty good with computers, but i dont know if he tried to do what you did, or if he even found any tutorial for this kind of way to repair it...if this ever happens again, i´ll definetly try to use your video! great work!
awesome video - finally someone that can explain the basics of this function - that said any suggestions when a message pops up to say DISM does not support a Windows Vista or earlier operating system. Thing is I have a Windows 10 I am trying to fix that is from 2022 and the iso image is 2023/4. I followed everything you had shared getting all the drive letters correct. I have to recover my system offline using a recovery disk - woke up next day with my computer unable to boot. I use UEFI to boot and I checked the EFI boot files etc and that is all in order now.
Most of my windows boot problems were hardware issues… like rams and HDDs but unfortunately i had to go through all the software diagnostics and possible fixes before realizing it was damaged hardware.. i think windows is developing a habit of destroying your memory with every release…. I have a drawer in my office full of pc and laptop RAMs also my humble advice for anyone using hdds .. clone your boot drive once every month or two onto an ssd or a spare drive ..
I've been a tech for years and never knew how to properly use sfc BTW I would use diskpart to list the disks to find out which drive is which or open regedit and export a key so you can get the dialog box that shows you drives...
I am having a problem with a windows update KB5025221not installing and it is keeping other updates from installing. I ran the Dism restorehealth command as per the previous video but got the following error DISM fails The source file could not be downloaded.
Thank you for this video. Unfortunately, I run into this error response when I try to run the DISM: "Error 87 The /Image option that is specified points to a running Windows installation. To service the running operation system, use the /Online option" What am I doing wrong?
I tend to use the chkdsk command with this to fix a lot of issues with friends and families Pc and it’s been a good combo fixing boot problems and windows problems….
So I am an IT guy since 30 years for quite a few companies, many hundreds of systems... and it is literally now over a decade i needed DISM or SFC or any other tool to restore Windows files. I am curious: what exactly do people do to ruin their Windows in a way that DISM would help? I mean as a normal user they can't overwrite anything, even as an admin you can't overwrite the system files, since you are not "TrustedInstaller". And if a Windows Update fails due to power outage or crash or anything while updating, NTFS will roll the changes back. So what do people do nowadays since ~Windows Vista to be able to ruin Windows files at all? Really curious :)
Problem is even if you use it, it doesn't work. By the way do you know how you can make a backup of Windows 8.1 with the programs you have installed and their configurations?
I'm not sure how the Windows image gets corrupted. It could be numerous things. It could be a bad drive, a bad Windows update, or just Windows eating itself (corrupting its own files). I typically spend the majority of my time figuring out how to fix it and spend very little time trying to figure out how it happened.
combination of unstable 'gamer brand' RAM and motherboards with onboard unstable 'gamer brand' chipsets System messes up on its own over time. 🤷♀️ The user can even be some random USPS-mailman who never uses it for more than a minute a month to pay bills and then something silly like the navigation pane in explorer will just disappear permanently until SFC fixes it. Odd stuff like that. TrustedInstaller is as inbred as a duke on an unstable system xD
@@CyberCPU Fair enough... would be so interesting to me, how it happens. So if at one point you do find the time to see how it happened I would love to see a video about it - probably will help many as well :)...
your videos are very usefull realy .....and explain good.....and how you explain it even i am not good in english !!! thnak you, some peopl, you give us a very confortable to do it. thnak you a lot off !!!!
My Windows 10 won't start. Safe mode too. BSOD - CRITICAL PROCESS DIED. I try to use DISM but keep getting error 0x800f0801. Do you have an idea how to deal with it?
I think to myself what if Windows not booting? after watching your first video. today saw your 2nd vid :D thanks a lot for the answer. like to ask - do we need the exact version of Windows? i hv Windows 10 Pro on my usb, but most of my friends hv Home version. will it work?
Home/pro doesn't matter. All Windows install USBs will have home and Pro. The correct build of Windows would be a good idea. However, not all files change in every build, so a different build isn't a deal breaker. It might work still.
i got this message: there is system repair pending which requires reboot to complete, restart windows and run sfc again, when i restart the min windows logo shows i get blue screen of death 😢
I do not want to repair my internal HD but and external HD that I have connected using SATA-USB cable to another USB port. That possible? I should then refer to that external HD in each of the commands you enter?
I had to do this just last week because I deleted a boot partition that was showing as an extra boot device in my Bios but only when the bios was in easy mode which was weird. In a program called "Easy EFUI" it was listed as hidden and I made sure it was the one I didn't need but when I deleted it bam my windows would no longer boot. I did not know about this video back then but when I made the recovery thumb drive and tried to do the start up repair as well as SFC and it failed and gave me an BSOD error that said could not fix disk or something and then gave some generic exception code. I eventually and I still don't really know how I did it used diskpart to rebuild the MBR I think, and even getting a few errors on the steps I followed from the internet, I somehow magically managed to get it fix lol. I think I did the same steps as in the video but in a different way?🤷♂ Anyhow I'm back up and running again and have once again learned never to mess with partitions at least not to delete any when I don't really know what I'm doing. I am glad though I did have enough primitive knowledge to at least fix it and the best part is the extra boot device no longer shows up in my bios as an option, was quite along day though. LOL
@@aravitz857 I don't know of a way to repair a broken registry without just restoring a backup. That's why I recently did a video on how to reenable registry backup. The system that inspired that video had to be reloaded.
Something is wrong. I tried all your recommendations for DISM and it still says "the source files could not be found. Use the "source" option to specify the location of the files that are required to restore the feature." and then it specifies a Microsoft link. Confusing...
This issue occurs because Microsoft's 'install.esd' file comes packaged with multiple versions of Windows (Home, Pro, etc.). When using the DISM command in the video, DISM fails as a result. It worked in the video because as he states @ 3:52 "...I'm not gonna do that because I've already created one for myself." It seems he created a Windows install USB in a different manner from in the video or he created one a long time ago before Microsoft started bundling multiple versions within a single .esd file. We can fix this problem with a couple extra commands. For this entire demonstration, assume your Windows boot drive is C:, your Windows install USB is D:, and your scratch directory is 'C:\Temp'. Make sure to make modifications to any of these following commands if you're using alternate paths. First we need to extract the correct Windows image from the 'install.esd' file. Type the following command into CMD: DISM /Get-WimInfo /WimFile:D:\install.esd This command will output the 'index' values for each version of Windows within the 'install.esd' file. Make note of the index value that correlates to your Windows version. As of the Windows 10 22H2 MCT .exe, Windows 10 Home is index 1 and Windows 10 Pro is index 6. For the rest of the demonstration, let's assume you're using Windows 10 Home so we shall use index 1. Now that we have the index value of the Windows version we need, let's extract it. We can extract it to the flash drive or the boot drive. For this demonstration, let's extract to the boot drive. DISM /Export-Image /SourceImageFile:D:\sources\install.esd /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:Max /CheckIntegrity This extracts the Windows 10 Home image file to the root of the boot drive (C:) as a '.wim' file. The '/SourceIndex:1' switch specifies the index for the Windows version, '1' is the index for Windows 10 Home; if you're not using Home (Pro, etc.) then change '1' in this switch to the correct index value that we retrieved earlier. The '/Compress:Max' switch compresses the '.wim' file to use less space but will take longer to do; if you don't mind using more space, you can use '/Compress:Fast' or '/Compress:None'. Now we can actually fix the issue! DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:C:\install.wim /ScratchDir:C:\Temp If you still get the error, check your syntax carefully and attempt the above command one more time (Hint: press the 'Up' arrow key on your keyboard to retrieve the last executed command). If you still get the error even after checking your syntax and trying again, attempt to re-export the 'install.esd' file using the '/Export-Image' command but this time use 'Compress:None'; this will take up far more space but may fix any compression/decompression errors that may have occurred. This works for Windows 11 too! Hope this helps!
I tried this method booting from an USB drive as you mentioned, but when I run DISM command, I always get this error: 0x800f081f. Any suggestions? Thanks in advance.
This issue occurs because Microsoft's 'install.esd' file comes packaged with multiple versions of Windows (Home, Pro, etc.). When using the DISM command in the video, DISM fails as a result. It worked in the video because as he states @ 3:52 "...I'm not gonna do that because I've already created one for myself." It seems he created a Windows install USB in a different manner from in the video or he created one a long time ago before Microsoft started bundling multiple versions within a single .esd file. We can fix this problem with a couple extra commands. For this entire demonstration, assume your Windows boot drive is C:, your Windows install USB is D:, and your scratch directory is 'C:\Temp'. Make sure to make modifications to any of these following commands if you're using alternate paths. First we need to extract the correct Windows image from the 'install.esd' file. Type the following command into CMD: DISM /Get-WimInfo /WimFile:D:\install.esd This command will output the 'index' values for each version of Windows within the 'install.esd' file. Make note of the index value that correlates to your Windows version. As of the Windows 10 22H2 MCT .exe, Windows 10 Home is index 1 and Windows 10 Pro is index 6. For the rest of the demonstration, let's assume you're using Windows 10 Home so we shall use index 1. Now that we have the index value of the Windows version we need, let's extract it. We can extract it to the flash drive or the boot drive. For this demonstration, let's extract to the boot drive. DISM /Export-Image /SourceImageFile:D:\sources\install.esd /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:Max /CheckIntegrity This extracts the Windows 10 Home image file to the root of the boot drive (C:) as a '.wim' file. The '/SourceIndex:1' switch specifies the index for the Windows version, '1' is the index for Windows 10 Home; if you're not using Home (Pro, etc.) then change '1' in this switch to the correct index value that we retrieved earlier. The '/Compress:Max' switch compresses the '.wim' file to use less space but will take longer to do; if you don't mind using more space, you can use '/Compress:Fast' or '/Compress:None'. Now we can actually fix the issue! DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:C:\install.wim /ScratchDir:C:\Temp If you still get the error, check your syntax carefully and attempt the above command one more time (Hint: press the 'Up' arrow key on your keyboard to retrieve the last executed command). If you still get the error even after checking your syntax and trying again, attempt to re-export the 'install.esd' file using the '/Export-Image' command but this time use 'Compress:None'; this will take up far more space but may fix any compression/decompression errors that may have occurred. This works for Windows 11 too! Hope this helps!
Dism /get-wiminfo /wimfile:x: (usb letter) \install.esd doesnt works neither wth esd, neither with wim it says "error:2, can't file dthefile... Am I at a dead point? Or can i extract it with my notebook?just try on notebook and got samecerror 😔😔😔😔😔
Ok, I've extracted the install.wam I need and put it on an usb key with no compression. Still get the 0x800f081f "impossible find the source file" after it reached 100%.I'm pretty sure I have windows 11 Pro. Ihave the old old ol key that I used to install, I will try again with tat... The log is a poem, and it says I have corrupetpted files... But if dism is needed to repair them....
My last pc wouldn't have worked with this. For some reason not only it doesn't boot, but it doesn't boot in recovery and if I put a bootable usb I get a broken screen and it never starts.
I had to physically swap the hard drive with another one with an OS installed on it for it to boot again, btw And it still doesn't boot from usb, always broken screen. It boots from dvd tho.
This issue occurs because Microsoft's 'install.esd' file comes packaged with multiple versions of Windows (Home, Pro, etc.). When using the DISM command in the video, DISM fails as a result. It worked in the video because as he states @ 3:52 "...I'm not gonna do that because I've already created one for myself." It seems he created a Windows install USB in a different manner from in the video or he created one a long time ago before Microsoft started bundling multiple versions within a single .esd file. We can fix this problem with a couple extra commands. For this entire demonstration, assume your Windows boot drive is C:, your Windows install USB is D:, and your scratch directory is 'C:\Temp'. Make sure to make modifications to any of these following commands if you're using alternate paths. First we need to extract the correct Windows image from the 'install.esd' file. Type the following command into CMD: DISM /Get-WimInfo /WimFile:D:\install.esd This command will output the 'index' values for each version of Windows within the 'install.esd' file. Make note of the index value that correlates to your Windows version. As of the Windows 10 22H2 MCT .exe, Windows 10 Home is index 1 and Windows 10 Pro is index 6. For the rest of the demonstration, let's assume you're using Windows 10 Home so we shall use index 1. Now that we have the index value of the Windows version we need, let's extract it. We can extract it to the flash drive or the boot drive. For this demonstration, let's extract to the boot drive. DISM /Export-Image /SourceImageFile:D:\sources\install.esd /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:Max /CheckIntegrity This extracts the Windows 10 Home image file to the root of the boot drive (C:) as a '.wim' file. The '/SourceIndex:1' switch specifies the index for the Windows version, '1' is the index for Windows 10 Home; if you're not using Home (Pro, etc.) then change '1' in this switch to the correct index value that we retrieved earlier. The '/Compress:Max' switch compresses the '.wim' file to use less space but will take longer to do; if you don't mind using more space, you can use '/Compress:Fast' or '/Compress:None'. Now we can actually fix the issue! DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:C:\install.wim /ScratchDir:C:\Temp If you still get the error, check your syntax carefully and attempt the above command one more time (Hint: press the 'Up' arrow key on your keyboard to retrieve the last executed command). If you still get the error even after checking your syntax and trying again, attempt to re-export the 'install.esd' file using the '/Export-Image' command but this time use 'Compress:None'; this will take up far more space but may fix any compression/decompression errors that may have occurred. This works for Windows 11 too! Hope this helps!
1. Is this process called "imaging" when IT technicians say they have to re-image the machine? 2. Do I have to back-up my personal files and data before running these tools? Does it affect my personal files and data in the same partition?
Thanks, I wish I had this tutorial before. 'Cause, I usually use _chkdsk_ commands to fix my drive or partitions inside the recovery, and most of the time it would fix the problems but it would take a lot longer, my last resort would be either *reset this pc* or reinstalling windows. I use it if I'm stuck on startup or loading screen due to sudden power outages or drive bad sectors.
Hey Yo! Per your video "Water Cooling a mid-range Graphics Card" It's too late, I spent $589 on an ASUS RTX3060 Ti. It works great, but when I'm streaming/gaming it gets 82c and I am thinking maybe an extra $200 for a kit would serve me well; taking off 30c temp. Lession I learned: The future of gaming needs more than 8GB VRAM. I'm Resigned to 1080p/ultra, but I think I can add value by by stabilizing my RTX temps. What do you think? I would've posted on your other video, but comments were limited 😂
I run most games on my 3060 at 3440x1440 to match my ultra wide. I'm very happy with the water block. It was definitely worth it. However, it's hard to find water blocks for mid-range GPUs. Most manufacturers don't make them. Not sure what you mean by comments being limited.
@@CyberCPU I've never water cooled my system before, and I wonder if it would be a weird change. What happens if I forget to turn my pump on, or I forget to top off my water reservoir? Wouldn't that spell disaster for the expensive GPU? Kinda scary for me to think about ;) It wouldn't let me post a comment on your other video for whatever reason. 🤷♂️ Anyway, thanks for your response 💯
@@DaKloneLiving That's weird that it wouldn't let you comment on the other video. I'm not sure why. When you water-cool a system the pump and everything comes on with the power button just like your air cooler. If done properly with high quality parts it should be fine. It takes a LONG time for water to evaporate from the reservoir. My main system was flushed and topped off well over a year ago and I haven't touched it. It runs every day. No problems.
I get: Deployment Image service and management tool: Error: 433 Unable to access the image. Make sure that the image path and the windows directory for the image exist and you have read permissions on the folder.
So like the motherboard manufacture instructions or whatever are they supposed to be in the box? I bought my laptop like 5 years ago… i have no idea where that is… is there a place online where you can find that info?
Amazing advice mate. Pssed I sent mine the india to get it up and running again. Come to think about it, never realised till now, 2 years have gone fast I wonder if they've managed to fix it for me. I didn't get a phone number from them. But what the hey!! They'll call me 😅😢😂
For me it keeps throwing me an error saying that the source files can't be found even when specifying source should be on my USB drive. Sfc command did say it found some errors and fixed them but after booting my windows still starts to load meaning I see the loading circle going but then it just restarts. I even tried fixing the bcd but nothing seems to work. About five years worth of work, bookmarks, files etc down the drain I guess 😭
