Page 11 of 36 FirstFirst ... 91011121321 ... LastLast
  1.    2015-10-08 #100

    Shadow Delta said: View Post
    Yeah. This was the command i ran and it ended up in error just as the previous user and like countless others. I searched around via Bing and google yet there is no depiction of a working fix or a definition why or what this error is any where.
    The install.wim you get in the ISO from the media creation tool does not work (you still get an install.wim not an .esd - but it is compressed and fails with 0x800f081f "The source files could not be found").

    You need to download the ISO from Tech Bench to use the /source option in dism.

    You could try using that one and see if it helps...
      My System SpecsSystem Spec


  2. Joined : Oct 2013
    NW Florida
    Posts : 6,493
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       2015-10-08 #101

    This is my download from the media creation tool. But, a new download wouldn't hurt.

    Click image for larger version. 

Name:	DISM.JPG 
Views:	261 
Size:	56.7 KB 
ID:	41762
      My System SpecsSystem Spec

  3.    2015-10-09 #102

    essenbe said: View Post
    This is my download from the media creation tool. But, a new download wouldn't hurt.

    Click image for larger version. 

Name:	DISM.JPG 
Views:	261 
Size:	56.7 KB 
ID:	41762
    That only worked as there is nothing to repair. You get the error with /source if there is something to repair and the source you specified doesn't have it (for example from Windows update). Try renaming some .dll to .bak and retry.

    The problem is (I think) dism does not recognize compressed .wim. @Kyhi knows better - he helped me out here.
      My System SpecsSystem Spec


  4. Joined : Feb 2015
    Bamberg Germany
    Posts : 12,362
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
       2015-10-09 #103

    halasz said: View Post
    That only worked as there is nothing to repair. You get the error with /source if there is something to repair and the source you specified doesn't have it (for example from Windows update). Try renaming some .dll to .bak and retry.

    The problem is (I think) dism does not recognize compressed .wim. @Kyhi knows better - he helped me out here.
    SFC(System File Checker) repairs those, not DISM.
    When you patch files(not a memory patcher) for a theme, using Resource Hacker or the like. that's how you bring your system back to "normal".
    For example I have a skin for WMP and if I don't rename the modified wmploc.dll file to .old or bak or .goofy(something not recognized by windows), it is wiped out and replaced with the correct wmploc.dll and I have to recopy it from my themes library I have created.
      My System SpecsSystem Spec

  5.    2015-10-09 #104

    I thought (sorry if this is wrong)

    • sfc checks things in system32 (which is what you use whether 32 or 64 bit) against what is in WinSxS (and replaces it if required)
    • dism (without /source) tries to replace incorrect WinSxS objects (via internet) with the correct version of the object based on some unknown criteria (presumably what you have installed). If it can't find a match - it fails.
    • dism (with /source) tries to replaces WinSxS with the source you specified. If it can't find it - it fails.


    Perhaps not
      My System SpecsSystem Spec


  6. Joined : Feb 2015
    Bamberg Germany
    Posts : 12,362
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
       2015-10-09 #105

    halasz said: View Post
    I thought (sorry if this is wrong)

    • sfc checks whatever is in system32 (which is what you use whether 32 or 64 bit) against what is in WinSxS (and replaces it if required)
    • dism (without /source) tries to replace WinSxS (via internet) with the correct version of WinSxS based on some unknown criteria (presumably what you have installed).
    • dism (with /source) tries to replaces WinSxS with the source you specified.


    Perhaps not
    That's where the dynamic link libraries are though, other wise I believe your correct.

    Source: http://www.thewindowsclub.com/winsxs-folder-windows-7-8
    [The Winsxs folder, stores multiple copies of dll‘s in order to let multiple applications run in Windows without any compatibility problem. If you browse inside, you will see what look like a lot of duplicate dlls, each having the same name. These are actually, different versions of the same files which are being stored; as different programs may require different versions.
    As mentioned, Windows stores the old dll‘s and library components in the WinSxS folder. Now if a newer version of this file is a part of the OS, but a particular application requires a particular older version for running, then the older version from the winsxs folder will be used, leaving the newer version in its present place, for other applications which may require it.So obviously you cannot delete this directory or move it elsewhere. Nor is it advisable to delete anything here, as such a step could probably make your applications un-workable or even break your system! If you have many applications installed, you can expect to have a jumbo sized winsxs folder. This WinSxs folder cannot reside on any other volume than the system volume. This is because of the NTFS hard links. If you try to move the folder, it may result in Windows updates, service packs, features, etc, not installing correctly.If you delete components from the WinSxS folder like the manifests or the assemblies, etc, you could be in trouble. Each system would react differently. What may work for one could break another! For instance, if you install a program that requires that particular assembly, which you may have deleted, then that program will just not run! Compressing the folder is also a no-no, as it could cause problems during WindowsUpdates or while installing a Hotfix.The safest way to clean it, is by simply uninstalling applications which you don’t require. However, this too is not fool-proof, as many applications still leave behind their files here, since they may be shared between other applications. So the probability of dud unused dll‘s being left behind is quite high.We would not advice the use of WinSxS cleanup tools like WinsxsLite as you could end up breaking your Windows.And if you are into trying out new software or installing and uninstalling frequently, you may notice that your Winsxs size is indeed large, as Windows will store multiple copies of these dll files, in order to let multiple applications
    So basically correcting the .dll has no effect on some copies in WinSxS. I hope this helps you a bit. Of course I could be misunderstanding it!!!
      My System SpecsSystem Spec

  7.    2015-10-09 #106

    Cliff S said: View Post
    So basically correcting the .dll has no effect on some copies in WinSxS. I hope this helps you a bit. Of course I could be misunderstanding it!!!
    So if the correct object doesn't exist in WinSxS (for some reason of corruption) and it doesn't exist (or is wrong version) in your /source as you have done a Windows update then what?

    You have to either rely on Windows Update (which would have worked without /source) or manually add the cumulative packages to your .wim.

    Seems a bit complicated to me.
      My System SpecsSystem Spec


  8. Joined : Feb 2015
    Bamberg Germany
    Posts : 12,362
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
       2015-10-09 #107

    One can't even clean up the WinSxs folder(Windows Update) anymore running cleanmgr.exe sageset:10 in the Run dialog for Disk Cleanup.
    A bit more on what DISM does/can do: What Is Deployment Image Servicing and Management? (Standard 8)

    I'm not quite "up" on that. If you understand what I mean.

    Common Servicing and Management Scenarios


    Image servicing and management solutions fall into the following two main categories:

    • Managing the data or information included in the Standard 8 image, such as enumerating or taking an inventory of the components, updates, drivers, or applications in an image.
    • Servicing the image itself, including adding or removing driver packages and drivers, modifying language settings, and enabling or disabling Standard 8 features.

    Limitations






    • Installing CBS packages to a remote computer over a network is not supported. The Standard 8 image must be present on the local system. DISM can access CBS packages on a network share but it must copy them to a temporary, writable scratch directory. We recommend using a unique scratch directory on a local drive for each CBS package you install. The contents of the scratch directory can be deleted after installation.
    • When you specify a configuration file (Unattend.xml) for an image, only the settings specified in the offlineServicing configuration pass are applied. All other settings in the configuration file are ignored. For more information, see Unattended Servicing Command-Line Options.
    • DISM can install only .cab files, .emd files, .msu files, and .inf files.
    • Some CBS packages require other CBS packages to be installed first. Because of this dependency, you should use a configuration file if you are installing multiple CBS packages. By applying a configuration file by using DISM, multiple CBS packages can be installed in the correct order. This is the preferred method for installing multiple CBS packages.
    • CBS packages are installed in the order they are listed in the command line.
    • The commands and options available for servicing an image depend on which Standard 8 operating system you are servicing, and whether it is an offline image or a currently running operating system.
    • You can specify more than one module, driver, or CBS package on a command line. However, multiple Unattend.xml configuration files are not supported. Only a single configuration file can be specified on any command line.
    • You can specify multiple modules, drivers or CBS packages but you cannot specify multiple commands (such as /Add-Driver /Remove-Driver or /Add-Driver /Add-Package) on the same command line.
    • When you use a computer that is not joined to a network domain, you must use net use with domain credentials to set access permissions before you specify the path for the DISM log stored on the network share.
    • Wildcards are not supported in DISM command line operations.
    • Files or directories copied to a target device when adding a custom module through DISM may be hidden. In order to see these files, the user should change the system attribute to display system and hidden files.

      My System SpecsSystem Spec


  9. Joined : Jun 2015
    Posts : 204
    Windows 10
       2015-10-26 #108

    Someone could explain, clearly, what are the Windows components and their store?

    It is possible to run the various DISM commands the first post when Windows 10.x boots?

    Thanks

    Bye
    Last edited by balubeto; 2015-10-26 at 06:07.
      My System SpecsSystem Spec


  10. Joined : Oct 2013
    Posts : 16,588
    64-bit Windows 10 Pro build 14986
       2015-10-26 #109

    Hello Balubeto,

    The component store basically is what SFC uses to repair system files from.

    None of the commands in the tutorial can be used at boot.
      My System SpecsSystem Spec


 
Page 11 of 36 FirstFirst ... 91011121321 ... LastLast


Similar Threads
Tutorial Category
SFC Scannow or DISM/RestoreHealth using Image
Windows 10 user. Having some trouble with my system after coming back from a weekend. Nothing major...just having trouble playing some games that require plugins etc Regardless if it's related, I just wanted to run an SFC/Scannow or...
Performance & Maintenance
How to repair your system files using Dism and Sfc in build 10041
Hello, everyone, I've managed to resolve most of my problems with build 10041 by making SFC work. I've opened a thread on Windows Insider's forums explaining how to do it. Check it out:...
Windows Insider
Windows 10 Crashing on CLASSPNP.SYS in safemode and startup repair.
I've just upgraded Windows 7 64-bit HP OEM to Windows 10 Technical preview 64-bit. Extracted the install while booted within 7, install went smoothly, opted to keep all my files, and once the install was finished it went to boot Windows 10. It hung...
General Support
W10 Disk Image Utility Reports Error After Image Creation.
I installed the 32 bit version of W10 on an old Acer laptop to get back up to speed with developments, and one of the first questions or issues that cropped up is when using W10's disk image utility to make a system image. I deliberately wished to...
General Support
Windows 10 TP Repair and Recovery Features
I'm currently running the 10 TP in a virtual machine. I see that the various boot and repair options can be accessed by <shift> Restart from the desktop, however F8 during boot doesn't appear to work. Can someone who is actually running this on...
Installation and Setup
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 15:25.
Find Us
Twitter Facebook Google+



Windows 10 Forums