Search the Community
Showing results for tags 'dism'.
-
I've made a short script that uses CHKDSK, DISM, and SFC to fix many common Windows-related** problems. The download is at the bottom and here's the whole "code" so you can see it's not something malicious. I've tried explaining each step. The script needs to be run as administrator in order to work properly. Hope this helps at least some of you. ** This script does not apply to Windows 7, some commands are newer. Should work fine on Win 10 and 8.1. @echo off color 0C title WinFix script for LinusTechTips forum members made by 191x7 echo !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! echo ! The script contains 4 procedures. echo ! The 1st procedure checks the disk - regular Checkdisk - 1 phase echo ! The 2nd procedure checks and repairs the Windows Component Files - 2 phases echo ! The 3rd procedure checks and repairs the Windows image - 4 phases echo ! The 4th procedure uses System file check to check system files - 1 phase echo ! In Windows 7 only CHKDSK and SFC work, the rest is new (Windows 8 +) echo !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! echo PRESS ANY KEY TO CONTINUE. pause >null del null cls echo ------------------------------------------------- echo Checking the Windows partition - procedure 1 of 4 echo ------------------------------------------------- chkdsk c: /scan echo ------------------------------------------- echo If it finds some problems, run chkdsk c: /f echo ------------------------------------------- echo PRESS ANY KEY TO CONTINUE. pause >null del null cls echo ------------------------------------------------ echo Windows component files check - procedure 2 of 4 echo ------------------------------------------------ Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase echo -------------------------------------------------- echo Phase 1 of 2 completed echo -------------------------------------------------- Dism.exe /online /Cleanup-Image /SPSuperseded echo -------------------------------------------------- echo Phase 2 of 2 completed echo PRESS ANY KEY TO CONTINUE. pause >null del null cls echo -------------------------------------------------------------- echo Checking the integrity of the Windows image - procedure 3 of 4 echo -------------------------------------------------------------- DISM /Online /Cleanup-Image /CheckHealth echo -------------------------------------------------- echo Phase 1 of 3 completed echo -------------------------------------------------- DISM /Online /Cleanup-Image /ScanHealth echo -------------------------------------------------- echo Phase 2 of 3 completed echo -------------------------------------------------- DISM /Online /Cleanup-Image /RestoreHealth echo -------------------------------------------------- echo Phase 3 of 3 completed echo PRESS ANY KEY TO CONTINUE. pause >null del null cls echo ------------------------------------------------- echo Running System file check - procedure 4 of 4 echo ------------------------------------------------- sfc /scannow echo -------------------------------------------------------------------------------- echo If SFC found some errors and could not repair, re-run the script after a reboot. echo -------------------------------------------------------------------------------- echo PRESS F TO PAY RESPECTS. pause >null del null LTT WinFix by 191x7 v13.03.19.bat
- 10 replies
-
- windows repair
- sfc
-
(and 4 more)
Tagged with:
-
I really need help with this one as I've run out of ideas to try! All of the troubleshooting that I've tried has just led me down dead ends with various errors along the way. I have an HTPC / media server running a regular installation of Windows 10 on a Samsung 4TB 870 EVO SATA SSD (2 years old) and the PC froze on the lock screen to which I rebooted it, and haven't been able to get into Windows since. The SSD shows in the BIOS storage configuration, and also shows partitions and volumes when I boot the PC from a Windows PE USB stick, but does not show in the boot order. I've tried various troubleshooting methods including bootrec.exe, bcdboot, bcdedit, to no avail. Following one of the troubleshooting steps, I opened a file explorer window from Windows PE and the drive shows up, however, it does not show the storage bar, and does not allow me to access it at all, so it looks like I don't have read permission? 2 years ago I had a similar experience with the same computer with Windows on a ADATA M.2 SSD, but I could access it, but it was locked into read-only mode as it seemed to have died - don't know if this fate has occurred to me again or if it's something different. I would like to hook up the SSD to another system to see if I can diagnose it but I don't have the appropriate connections / alt. desktop with me. Any / all help is greatly appreciated!
-
- windows 10
- ssd
-
(and 3 more)
Tagged with:
-
A few weeks ago I launched Witcher 3 and noticed that the game was really laggy, constant FPS drops. I restarted the game, and on the 2nd try the entire PC just went dark and rebooted... Event viewer told me the graphics card/driver crashed. Before it put me at the login screen, it shortly mentioned something about updates. So before troubleshooting the GPU I checked Windows Update and saw an update for "Steelseries - Aps". I installed it and rebooted, and then it got stuck for over an hour on "Working on updates, do not turn your PC off" with no progress bar. I got back in and checked event viewer which was just spammed with "DCOM got error "1115" attempting to start the service UsoSvc with arguments "Unavailable" in order to run the server" throughout the "update" and then an error about Windows Module Installer force quitting. I've tried googling this but I haven't got any luck figuring out what causes it. And after this I've been unable to install any updates other than Defender definitions... They all get stuck on downloading at 4%, next reboot they're at 0% installed, then next boot they're "installed" and this cycle repeats with every restart. And in-between every single reboot it gets stuck at the updates screen for 60-70 minutes, but shutting down works fine? I've tried: Running sfc /scannow which found corruptions at first but now nothing. DISM /Online /Cleanup-Image /RestoreHealth just goes blank without a progress bar, but checking the cbs.log it seems to be running? Either way it's stuck blinking in the cmd and stops with some of these errors: Sometimes the progress gets further, but it always just stops like this. Seems to be the same when I try to download a new update. Running the WU troubleshooter, it just keeps saying there's a pending restart when there's not. And after clearing the WU download folder it just gets just stuck after telling me that now. Booted into safe mode with networking, and their DISM and the Windows Update troubleshooter finally seem to work, but I have no internet because the network card driver is disabled? I've tried running these commands from the Microsoft documentation(not the ones below that though), and it seemed to reset WU, but they still just get stuck doing nothing with further errors The only things that come to mind is to run DISM offline, but documentation for that is very scarce. And I don't know if running the Windows 11 upgrade tool will work either since WU is so broken... I'm really at a loss here. It's a completely fresh Windows 11 install that I've only used for 3 weeks and apart from the aforementioned I don't know what to do apart from re-installing completely, which I'd really like to avoid since I just finished setting everything up. Does anyone have any idea on how to fix this?
- 1 reply
-
- windows 11
- windows update
-
(and 3 more)
Tagged with:
-
One of my best friends, Kyo made a pretty nifty backup script using DISM to make 1:1 backups of your Windows Install, Drive or Folder and saving them as .wim file! It makes it super easy to reinstall your current OS with all its data and programs to a new SSD/HDD really easy! It runs rather fast too, once you put DISM.exe into your Windows Defender Exceptions (Defender keeps scanning this process, slowing down the backup process drastically. Dont worry about safety, DISM is a windows tool and process) Here is Kyo's Github page of the script: https://github.com/KyodaiKen/DISMBackup#restore-complete-windows-drive-and-make-it-boot I have been using it for over a year now and it never let me down. I thought I share it with you nerds :3
-
I decided to test-flight the Windows 11 Beta. I got my filthy hands on the ISO. So far so good. Now, I'm used to just dumping the ISO content onto a GPT/FAT32 partition and UEFI boot off of it. But this ISO is not making it easy. The install.wim file is over 4GB in size and as such cannot be copied to a FAT32 volume. I google-fu'd a solution, which was to use DISM to split the wim into multiple files. Fair enough, I have do my share of DISMing back in the day (turns out these DISM operations have a pretty neat PowerShell analogs these days, and one feels more like a pro using those, right?: https://docs.microsoft.com/en-us/powershell/module/dism/split-windowsimage?view=windowsserver2019-ps). This installer (with the split wim files sneaked into the relevant folder (sources) instead of the install.wim) boots fine, but the installation falls on its face prematurely with an error some 2% into the 'copying files' part. Now, this might be due to the split wim image, I don't really know, maybe there were more steps to follow after the splitting that I overlooked . Now, I'm a resourceful boi so this didn't stop me, though the following step might feel like a bit of an overcomplicated reach-around: I have - created a virtual machine in Hyper-V (has to be Gen 2 if we want it to UEFI boot, which we do) - loaded the original Win11 ISO into the VM's emulated optical drive - attached one of my physical drives to the VM (my other, non-system M.2 NVMe disk) - this is done by first making it offline in Disk Management, then adding it to the VM - booted the VM from the ISO - started the Windows 11 Beta installation to the attached disk - wait for the first (or the second is fine, too) reboot phase and shut down the VM - booted up my PC from the SSD that was in the middle of the install process - It picked up from there Anyway. This is how I managed to handle my 'installer media' problem. This may be helpful to someone with a similar problem, or you can share if you have a different solution (as long as it's not burning the ISO to an actual DVD - it's 2021 ffs!). Hmm, maybe I could have just 'imaged' the ISO onto an external USB flash drive? But in my experience those tools don't always work as they should.
-
Hello everyone! I have a TrueNAS Server with a Windows Server 2022 VM installed on it that runs WDS. I made a fresh install of Windows 11 21H2 on my main PC (on a secondary SSD) so that I can install some software and make it into a custom Windows image for WDS using Audit Mode and then DISM in Windows PE (Windows 11 Installer). My problem is, when my fresh VM starts up after Windows has been installed it always gives me the OOBEREGION error after I select my region, this goes on until the username screen, that's where I can't skip the error anymore, I also tried to install the same image on my father's laptop using a spare SSD that I had laying around. Any sugestions on how to fix the custom image so that it works properly? Thanks! btw, I've (mostly) used this tutorial: https://theitbros.com/sysprep-windows-machine/
-
Problem : Am trying to get my system health report back to normal state. What i had done so far.. ran an elevated CMD / Powershell.. executed sfc /scannow.. Windows PowerShell Copyright (C) 2016 Microsoft Corporation. All rights reserved. PS C:\WINDOWS\system32> SFC /SCANNOW Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. but when i executed this "Repair-WindowsImage -Online -CheckHealth" results.. Path : Online : False ImageHealthState : Repairable RestartNeeded : False executing RestoreHealth.. PS C:\WINDOWS\system32> Repair-WindowsImage -Online -RestoreHealth Repair-WindowsImage : The restore operation failed. Either the repair source was not found or the component store cannot be repaired. At line:1 char:1 + Repair-WindowsImage -Online -RestoreHealth + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Repair-WindowsImage], COMException + FullyQualifiedErrorId : Microsoft.Dism.Commands.RepairWindowsImageCommand cutting story short.. i now have the acquired source file which is called install.wim (extracted from install.esd from windows ISO) executed lines of DISM code onto cmd/powershell..which is DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:F:\sources\install.wim:1 /LimitAccess Limit Access means windows update or WSUS are excluded as source.. end result is failed miserably.. refer the CMD image attached. i need some serious level 3 tech support here.. please no mentioning format/refresh/reinstall windows.
-
- windows 10 pro
- dism
-
(and 2 more)
Tagged with:
-
Hey all, My windows (1803) will not update to 1903. It will download and install but fail at 100. With error code 0xc1420121 and one other. I tried: Restarting, direct update, windows update assistant, restart, windows troubleshooter update, remove perihals, download 1903 as an iso didnt install. However DISM, restore health fails, and DISM says source files missing or corrupted. How do i fix this corrupution and would it impact the update? TLDR: 1903 update fails do due to potential image corruption
-
I'm trying to fix some corrupted files in my widows, idk how some softwares got corrupted, it was fine previous night. So I followed some guides, opened Command Prompt, used SFC /SCANNOW. And found there are some corrupted files present, so I used DISM /Online /Cleanup-Image /RestoreHealth to fix them, but it says: Now what, I searched the web and found that I need to manually download a copy of windows? and specify the source file of that windows? Idk, they didn't explain what I have to do, so I searched a little more and found this page which at least tries to explain what I have to do. But I need some help, I downloaded a version of windows and mounted it to I: using Daemon Tools and used the source command to specify the source, still no luck. Please help. Also, What does the Version and Image version mean? I'm also attaching a screenshot of the total mess in Command Prompt.
- 1 reply
-
- dism
- error 0x800f081f
-
(and 1 more)
Tagged with:
-
I'm on a fresh install of Windows 8.1, just upgraded to Windows 8 two days ago and installed 8.1 yesterday. Having issues getting Microsoft .NET Framework 3.5 installed. Things I've tried: Install from prompt after opening app that requires it (Puush)Returned 0x800f0906 error Install from enabling it in Windows Feature through Control PanelReturned 0x800f0906 error Install from media/windows 8 USBReturned 0x800f081f error Tried cleaning dism and restoring it's health to fix 0x800F081FYielded no results, giving same errors. Tried contacting Microsoft support Asked to pay $99 paid support, didn't want to pay for a supposed to be simple thing And I just BOUGHT Windows 8 yeah? downloading sxs file from the internet to install .NET Framework 3.5Returned same 0x800f081f error I'm out of options, at least that's all that my Googling power managed to find. Can someone assist me please? Thanks in advance Let me know if there's any other information that I should be giving. UPDATE First of all, thank you GoodBytes, you sir is a good man! Out of all the people I reached out on the internet, no one came around to assist even the slightest. After the suggestion on possibly having issues with the initial ISO I've upgraded my Vista PC with, I decided to re-download a clean, fresh ISO from Microsoft using the Windows 8 Installer. I proceeded to re-install Windows 8 and right after installing the OS, I didn't even bother with Chrome, which is what I normally always do first and continued to try and enable Microsoft .NET Framework 3.5 from Windows Features in the Control Panel. After about 2 minutes, it installed without a hitch! I don't know exactly what was wrong with the initial ISO provided by a friend of mine, but the freshly downloaded ISO installed the framework without a problem.