DISM restorehealth error 14098

We have a windows server 2012 box that is hosted remotely. I've been trying to install a security patch and the windows update component appears to be corrupted. The error code i'm getting is 80073712. It will download the updates but fails to install them.
Installing manually with msu file doesn't work either. So far the steps i've taken are
run the microsoft fix it tools. It says that it fixed the problems, but then it just fails again.
Rename/delete the SoftwareDistribution folder in the windows folder
Use the Dism command to try and repair it- dism /online /cleanup-image /restorehealth This cause an error 14098. The component store has been corrupted
Used the equivalent command in powershell
I downloaded a server 2012 iso directly from microsoft and mounted it to try and use the /source switch to repair using the iso. Now I haven't really seen a lot of good examples of what the syntax should be for this. This is the command i was trying to
use:
DISM /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:2
2 is the index number for server standard, which is what we are running. I get the same result, error 14098
Now i also tried this in powershell with this command:
Repair-WindowsImage -Online -RestoreHealth -Source:Wim:D\Sources\install.com:2. I get an error stating the component store is corrupted.
So i'm not sure where to go from this point. I don't even know if i have the syntax right for it to use the install disk as the source file. Any help is appreciated. If there is some other method i haven't thought about maybe

Hi BradSwink1,
Could you try to use elevated command prompt to run sfc /scannow and dism /online /cleanup-image /restorehealth, most times the corrupt files may cause the
14098 error.
The similar thread:
DISM /restoreHealth fails with 0x800f081f AFTER 8.1 update successfully installed
http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/dism-restorehealth-fails-with-0x800f081f-after-81/a83650a9-c515-4bb8-aa7d-298be85e7bc3
Windows KB2802618 update error, then DISM error 14098
http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_update/windows-kb2802618-update-error-then-dism-error/cb5d53e6-82dd-4064-b762-517268bcf158
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

Win 8.1 Pro dism /Online /Cleanup-Image /RestoreHealth returns Error: 14098

I am running Windows 8.1 Pro and have recently been experiencing some odd behavior. This has lead me to discover that my component store is corrupt.
I have attempted to use sfc with no luck and have posted that on a separate thread.
When I attempt to use dism /online /cleanup-image /retorehealth, dism quickly comes back with Error: 14098.
Event the dism log looks corrupt. Below is just the beginning of the file. the not English character portion continues and is quite large:
[2580] Caller did not request sparse mount
[2580] Mounting new image.
Wim: [\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim]
Image Index: [1]
Mount Path: [C:\WINDOWS\TEMP\c18ce950-f10f-4afc-a811-28b1ffe5b733]
[2580] Wimserv process started for guid b3e8550e-9dd9-4246-855b-f0ac5d1c531f. Id is 956
[956] ImageUnmarshallHandle: Reconstituting wim at
\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.
[956] Mounted image at C:\WINDOWS\TEMP\c18ce950-f10f-4afc-a811-28b1ffe5b733.
[2580] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2580] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2580] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2580] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[2580] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[2580] [0xc142011c] WIMGetMountedImageHandle:(2568)
[2580] ImageUnmarshallHandle: Reconstituting wim at
\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.
[2580] ImageUnmarshallHandle: Reconstituting wim at
\\?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE\Winre.wim.
〲㌱ㄭⴰ㠱ㄠ㨵㘲〺ⰷ䔠牲牯††††††††䐠卉⁍†䥄䵓䐠楲敶⁲慍慮敧㩲倠䑉㤽㈵吠䑉㈽㠷‸慆汩摥琠⁯湩瑳污⁬桴⁥牤癩牥瀠捡慫敧✠㩃坜湩潤獷卜獹整㍭尲牄癩牥瑓牯履
Is partition1 the "System Reserved" partition? Could it be corrupted and if so, can it be repaired or rebuilt?
Any ideas or help would be greatly appreciated.
Thanks,
Glen

Honestly this is something MS should check into. There should be an easier way for users to implement this command rather then a complete dictionary to fix broken windows files. This is a Microsoft windows problem. I know for myself I had to use this command
quite often because I installed something windows did not like. Because of that window files became unusable. It would make practical sense for Microsoft to incorporate a feature that runs these commands in administration tools.
Run
Dism /Online /Cleanup-image/ScanHealth
if that runs an error then run
Dism /Online /Cleanup-Image /StartComponentCleanup
then run
dism /online /cleanup-image /retorehealth
http://technet.microsoft.com/en-us/library/dn251565.aspx
Edit: Microsoft has to make a serious decision. During setup, Metro, or desktop. Installing items in desktop mode is creating errors in Metro or windows store items. In future upgrades consider the flavors of OS, implement a users
choice. Desktop, Metro, or classic. Face the facts if you follow Linux method of desktop, and the install process. There is no confusion between desktops and we have a choice. This makes common sense. I like the feature of gnome or Ubunto it gives
the user a choice and a better picture for Microsoft. Lets face it, Bill Gates choose to hand over his business to people. This gave Bill Gates time to help other people that need help. How about Microsoft do the same and give people the choice between
desktops during install. Follow Bill Gates important roll in his life now. Bring some fairness and happiness to people that like Microsoft and what to help users get what they want and the best support they need. Doing this allows Microsoft the glory
to help people feel good about themselves. Sure MS can live in a dictatorship roll and continue to bully users to use the product, there is a consequence to this. Good young developers are working on a better OS and this is going to happen. It is better
to help people then to fight people.

Error when running DISM /Online /Cleanup-Image /RestoreHealth - error 0x800f0906

Hello.
I wonder if you can help me.
I keep getting error 0x800f0906 when running DISM /Online /Cleanup-Image /RestoreHealth.
DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
relevant bits from it seem to be:
Checking System Update Readiness.
(p)   CSI Payload Corrupt           amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wuaext.dll
Repair failed: Missing replacement payload.
(p)   CSI Payload Corrupt           amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.8.9200.16927_none_28265fa316d944b7\wushareduxresources.dll
Repair failed: Missing replacement payload.
Summary:
Operation: Detect and Repair
Operation result: 0x800f0906
Last Successful Step: Entire operation completes.
Total Detected Corruption:   2
   CBS Manifest Corruption:   0
   CBS Metadata Corruption:   0
   CSI Manifest Corruption:   0
   CSI Metadata Corruption:   0
   CSI Payload Corruption:   2
Total Repaired Corruption:   0
   CBS Manifest Repaired:   0
   CSI Manifest Repaired:   0
   CSI Payload Repaired:   0
   CSI Store Metadata refreshed:   True
In adition, my windows 8 will not carry out a scheduled maintenance session.
Is this something I can repair. Any help would be appreciated. The setup event logs mentions 2 errors, so presumably this is the issue.

Use the "source" option to specify the location of the files that are required to restore the feature."
If we read the documentation, we might infer we can use any existing WinSxS as source?
http://technet.microsoft.com/en-us/library/hh825265.aspx
<quote>
You can restore and enable a feature that has previously been removed from the image. Use the
/Source argument to specify the location of the files that are required to restore the feature. The source of the files can by the Windows folder in a mounted image, for example c:\test\mount\Windows. You can also use a Windows side-by-side
folder as the source of the files, for example z:\sources\SxS.
If you specify multiple /Source arguments, the files are gathered from the first location where they are found and the rest of the locations are ignored. If you do not specify a
/Source for a feature that has been removed, the default location in the registry is used or, for online images, Windows Update (WU) is used.
Use /LimitAccess to prevent DISM from contacting WU for online images.
</quote>
That quote was actually from under the /Enable-Feature operand but the /Source: operand has wider scope.
Compare the briefer description of the same operand given later under the /Cleanup-Image operand
<quote>
Use /Source with /RestoreHealth to specify the location of known good versions of files that can be used for the repair, such as a path to the Windows directory of a mounted image.
If you specify multiple /Source arguments, the files are gathered from the first location where they are found and the rest of the locations are ignored. If you do not specify a
/Source for a feature that has been removed, the default location in the registry is used or Windows Update (WU) is used for online images.
Use /LimitAccess to prevent DISM from contacting WU for repair of online images.
</quote>
Does this mean the functionality is limited or that they were just trying to avoid being redundant?   ; }
Good luck
Robert Aldwinckle

DISM gives Error 11

I have been running MS systems since you needed to 5-1/4' floppies to boot them. I know the difference between 32-bit and 64-bit systems. This one has me a bit frazzled.
When I run Dism.exe, I consistently get the following error:
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Error: 11
You cannot service a running 64-bit operating system with a 32-bit version of DISM.
Please use the version of DISM that corresponds to your computer's architecture.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
It's obvious that the command that's loading is the 32-bit version. I scanned the hard drive and found several versions of DISM.exe. Each time I get the same error, regardless of which DISM.exe I execute. Each time I was in an "elevated" cmd environment.
I even tried going into Powershell and running it. Same problem. I have checked the path, just to be sure. sysWOW64 appears before system32 in the path variable. I have tried running dism.exe from each individual location on the drive, just to make sure
the "local" command is/was being executed. Same error.
The reason for this is that sfc /scannow found some corrupted files it could not repair. I wanted to run the DISM command, then rerun the sfc command.
Where can I find the 64-bit version of dism.exe? It should be on the hard drive somewhere or at least you would think so.
I also tried running Powershell and the Repair-WindowsImage -Online -RestoreHealth. It failed with a similar error.
Outside of these commands, I will likely have to restore Windows 8.1 and start over.
What prompted all this was the laptop started doing some flaky things. For example, when you try to open a cmd environment, the system would just stall and restart explorer.exe after a few minutes. This happened repeatedly. I was finally able to get a cmd
environment to open from the directory where the command is located. After that, it worked flawlessly. Similar things were happening trying to run other commands/features. This all started after installation of one of the MS security patches.
At this point, wiping the system and starting with a clean slate may be the best option.
Oh - system running Windows 8.1, latest patches. HP Laptop 750GB HD, 6GB RAM, i3 processor.
Bob
Bob C., OCP

Okay... don't take this wrong, but "I didn't fall off the truck yesterday"! I will admit that I had not tried the solution you suggested, but I do know how to open a command environment, etc. I tried your suggestion and that's when I got
the message below - "Access denied".
I think I have found the root cause of this problem:
I started perusing the system in general. I checked everything from A to Z. Then, it hit me when I got an error message "Access Denied..." message.
I checked my access to the system and found that my account (not the System Administrator account) had been changed from an Administrator to a Standard User. That's easy enough to fix. WRONG! I logged in as the Administrator and found that I could no longer
change an account from a Standard to an Administrator role. How this happened, I do not know. I have not gotten any viruses or malware - I check every week with Norton, then Malwarebytes. I know some things can get by one product, but there is a slim chance
that it would get by two products. But, I digress...
I checked the Administrator access to the suspect folders. The Administrator account has NO access to the Windows folder. I have full access to the "C" drive, but ZERO access almost all the subsequent folders. Yes, I can list folder contents, etc.
But, I cannot change anything. For example, the c:\windows folder is set to Read Only. Just for grins, I tried to change it... wouldn't allow it.
I did find that the only account that has FULL access to everything is the TrustedInstaller account. Sounds suspicious...
Okay, while still logged in as Administrator, I went to Control Panel>User Accounts>Manage Another Account and tried to change my "usual" account from a Standard User to an Administrator User. It won't let me, as the Administrator Role/User
is greyed out. Mind you, this is from the Administrator account to another user.
I found several instances of this on the internet. I have tried the "fixes" I found, but thus far it has been a "no go." I am beginning to think the only way out of this is a system refresh, i.e., backup all my files and re-install the
OS.
I am going to give this one final shot from a "clean boot" with network access. If that doesn't work, I am looking at a backup and reload.
Any ideas/suggestions will apprecisted.
Bob
Bob C., OCP

Inconsistent DISM.EXE error when applying unattend.xml during LTI deployment - Possible bug!

I've been using MDT 2012 and 2012 update 1 with ADK for Windows 8 successfully for years. This week I decided to uninstall those tools, and install ADK for Windows 8.1 and MDT 2013. I'm running Windows 7 x64. Instead of upgrading the current
deployment share, I created a new share to start fresh.
So, I created a new share, added Windows 7 OS, and created a client deployment task sequence. I modified the unattended.xml to enable telnet client and disable media center. No drivers, no applications, and no packages for this test. Stock, unmodified
task sequence.
Problem:
It works as expected sometimes. But, about 50% of the time, I get this error:
From the BDD.LOG:
<![LOG[About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="00:16:51.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1224)]LOG]!><time="00:16:51.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Deployment Image Servicing and Management tool]LOG]!><time="00:16:51.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Version: 6.3.9600.16384]LOG]!><time="00:16:51.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Image Version: 6.1.7600.16385]LOG]!><time="00:16:52.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Disabling feature(s)]LOG]!><time="00:16:53.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Disabling feature(s)]LOG]!><time="00:16:58.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Error: 0x80220013]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > DISM failed. No operation was performed. ]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > For more information, review the log file.]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > The DISM log file can be found at X:\windows\Logs\DISM\dism.log]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = -2145255405]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FAILURE ( 5627 ): -2145255405 0x80220013: Run DISM.exe]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="00:16:59.000+000" date="10-30-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
From the DISM.LOG:
2013-10-30 00:16:58, Error CSI 00000001 (F) 80220013 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=19 (0x0013)] #5# from CWcmEngineCore::GetNamespaceWithOptions(nsid = { name: Microsoft-Windows-PnpCustomizationsNonWinPE ver: lang: neutral arch: amd64 pkt: 31bf3856ad364e35 verSc: nonSxS }, iMode = 1, iAccess = 2, iOption = 1, target = @0x4c792c0, context = NULL, namespace = { name: Microsoft-Windows-PnpCustomizationsNonWinPE ver: lang: neutral arch: amd64 pkt: 31bf3856ad364e35 verSc: nonSxS })
[gle=0x80004005]
2013-10-30 00:16:58, Error CSI 00000002 (F) 80220013 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=19 (0x0013)] #3# from CUnattendDeserializer::ProcessComponentElement(...)[gle=0x80004005]
2013-10-30 00:16:58, Error CSI 00000003 (F) 80220013 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=19 (0x0013)] #2# from CUnattendDeserializer::ProcessDocument(...)[gle=0x80004005]
2013-10-30 00:16:58, Error CSI 00000004 (F) 80220013 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=19 (0x0013)] #1# from CUnattendDeserializer::Deserialize(stream = @0x40acf60, engine = @0x4301af0, target = @0x4c792c0, results = NULL, resultCount = 0)[gle=0x80004005]
2013-10-30 00:16:58, Error DISM DISM Smi Provider: PID=1264 Error deserializing SMI settings. - CSmiWrapper::ApplySettings(hr:0x80220013)
2013-10-30 00:16:58, Error DISM DISM Smi Provider: PID=1264 d:\w7rtm\base\ntsetup\opktools\dism\providers\smiprovider\dll\smimanager.cpp:166 - CSmiManager::Apply(hr:0x80220013)
2013-10-30 00:16:58, Error DISM DISM Unattend Manager: PID=1264 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:400 - CUnattendManager::Apply(hr:0x80220013)
2013-10-30 00:16:58, Error DISM DISM Unattend Manager: PID=1264 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:654 - CUnattendManager::InternalExecuteCmdLine(hr:0x80220013)
2013-10-30 00:16:58, Error DISM DISM Unattend Manager: PID=1264 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:603 - CUnattendManager::ExecuteCmdLine(hr:0x80220013)
2013-10-30 00:16:58, Error DISM DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80220013
I noticed that it never seems to happen if I don't enable/disable features with the unattended.xml
unattended.xml that has the problem:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="configure">
<assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="6.1.7601.17514" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" />
<selection name="TelnetClient" state="true" />
<selection name="TFTP" state="true" />
<selection name="FaxServicesClientPackage" state="false" />
<selection name="MediaCenter" state="false" />
<selection name="OpticalMediaDisc" state="false" />
</package>
</servicing>
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
<InstallFrom>
<Path>.\Operating Systems\Windows 7 Pro x64 SP1\Sources\install.wim</Path>
<MetaData>
<Key>/IMAGE/INDEX</Key>
<Value>1</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
<ProductKey>
<Key></Key>
</ProductKey>
</UserData>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<Credentials>
<Username></Username>
<Domain></Domain>
<Password></Password>
</Credentials>
<JoinDomain></JoinDomain>
<JoinWorkgroup></JoinWorkgroup>
<MachineObjectOU></MachineObjectOU>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName></ComputerName>
<ProductKey></ProductKey>
<RegisteredOrganization>Inc.</RegisteredOrganization>
<RegisteredOwner>Desktop</RegisteredOwner>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<TimeZone>Pacific Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Home_Page>about:blank</Home_Page>
<DisableWelcomePage>true</DisableWelcomePage>
<DisableFirstRunWizard>false</DisableFirstRunWizard>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>EnableAdmin</Description>
<Order>1</Order>
<Path>cmd /c net user Administrator /active:yes</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>UnfilterAdministratorToken</Description>
<Order>2</Order>
<Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>disable user account page</Description>
<Order>3</Order>
<Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-TapiSetup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TapiConfigured>0</TapiConfigured>
<TapiUnattendLocation>
<AreaCode>""</AreaCode>
<CountryOrRegion>1</CountryOrRegion>
<LongDistanceAccess>9</LongDistanceAccess>
<OutsideAccess>9</OutsideAccess>
<PulseOrToneDialing>1</PulseOrToneDialing>
<DisableCallWaiting>""</DisableCallWaiting>
<InternationalCarrierCode>""</InternationalCarrierCode>
<LongDistanceCarrierCode>""</LongDistanceCarrierCode>
<Name>Default</Name>
</TapiUnattendLocation>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableSR>1</DisableSR>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value>UABAAHMAcwB3AG8AcgBkAD0ANwBBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>UABAAHMAcwB3AG8AcgBkAD0ANwBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</Password>
<LogonCount>999</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<RegisteredOrganization>Inc.</RegisteredOrganization>
<RegisteredOwner>Desktop</RegisteredOwner>
<TimeZone></TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1" wcm:action="add">
<Path>\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
</unattend>
unattended.xml that is problem-free:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
<InstallFrom>
<Path>.\Operating Systems\Windows 7 Pro x64 SP1\Sources\install.wim</Path>
<MetaData>
<Key>/IMAGE/INDEX</Key>
<Value>1</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
<ProductKey>
<Key></Key>
</ProductKey>
</UserData>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<Credentials>
<Username></Username>
<Domain></Domain>
<Password></Password>
</Credentials>
<JoinDomain></JoinDomain>
<JoinWorkgroup></JoinWorkgroup>
<MachineObjectOU></MachineObjectOU>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName></ComputerName>
<ProductKey></ProductKey>
<RegisteredOrganization>Inc.</RegisteredOrganization>
<RegisteredOwner>Desktop</RegisteredOwner>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<TimeZone>Pacific Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Home_Page>about:blank</Home_Page>
<DisableWelcomePage>true</DisableWelcomePage>
<DisableFirstRunWizard>false</DisableFirstRunWizard>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>EnableAdmin</Description>
<Order>1</Order>
<Path>cmd /c net user Administrator /active:yes</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>UnfilterAdministratorToken</Description>
<Order>2</Order>
<Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>disable user account page</Description>
<Order>3</Order>
<Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-TapiSetup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TapiConfigured>0</TapiConfigured>
<TapiUnattendLocation>
<AreaCode>""</AreaCode>
<CountryOrRegion>1</CountryOrRegion>
<LongDistanceAccess>9</LongDistanceAccess>
<OutsideAccess>9</OutsideAccess>
<PulseOrToneDialing>1</PulseOrToneDialing>
<DisableCallWaiting>""</DisableCallWaiting>
<InternationalCarrierCode>""</InternationalCarrierCode>
<LongDistanceCarrierCode>""</LongDistanceCarrierCode>
<Name>Default</Name>
</TapiUnattendLocation>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableSR>1</DisableSR>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value>UABAAHMAcwB3AG8AcgBkAD0ANwBBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>UABAAHMAcwB3AG8AcgBkAD0ANwBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</Password>
<LogonCount>999</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<RegisteredOrganization>Inc.</RegisteredOrganization>
<RegisteredOwner>Desktop</RegisteredOwner>
<TimeZone></TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1" wcm:action="add">
<Path>\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
</unattend>
Please help!

To be honest, I've never tried to modify the installer packages via unattend.xml. And come to think of it, it appears that the /applyunattend switch may not understand how to install packages (might not know where the sxs folder is located ). What
is confusing to me is how it *does* work 50% of the time.
did you import the *full* sources or just the *.wim file?
Here is a post in the configmgr group which suggests to perform the package management *online*
http://social.technet.microsoft.com/Forums/systemcenter/en-US/42eb50b6-7059-431c-ae84-2e5753507a90/unattendxml-and-microsoftwindowsfoundationpackage
Keith Garner - keithga.wordpress.com
Thanks for the reply Keith.
I imported the full source, and I'm also not sure why it is not consistent with failure or success either.
To narrow down the problem, I created a reproducible set of steps (for a possible future call to Microsoft support). Those steps are described in this
thread. When following the steps in the thread, the problem appeared every time. I only tried it 6, or so, times though.
The enabling/disabling of features via the unattend.xml is a supported and documented feature. In fact, following the hyperlink in the solution of the thread you mentioned documents the process.
-Tony

Inject Drivers step fails, DISM application error

We've been imaging Surface 3 tablets for a while with SCCM 2012 R2 CU4 since CU4 came out. Recently the task sequence is failing while applying drivers. On the screen is a DISM.exe application error.
"The instruction at 0xa7356ccc referenced memory at 0x258d1a58. The Memory could not be read"
The SCCM task Sequence Error is 0xC0000005
I cannot find a DISM log, probably because it's an application crash. The SMSTS Log isn't much help either.
I've changed from apply driver package to auto-apply, refreshed Distribution Points for the driver packages and the boot images.
Our Windows 7 Task Sequences are unaffected. Seems to only be the Windows 8.1.

If you have UEFI enabled, have a look there:
http://deploymentresearch.com/Research/Post/333/Deploying-Surface-2-Pro-with-ConfigMgr-2012-SP1-CU3

Error 0x800f0203 when enabling Hyper-V on 8.1

I had Windows 8.0, disabled Hyper-V, and upgraded to Windows 8.1.
I'm trying to re-enable Hyper V now. I've successfully enabled / installed Hyper-V Manager, but Hyper-V Platform is errorring out.
I'm on a Lenovo W530 with updated drivers.
Relevant parts from my CBS log:
2014-01-27 17:00:05, Info CSI 000000a4 Begin executing advanced installer phase 38 (0x00000026) index 123 (0x000000000000007b) (sequence 162)
Old component: [l:0]""
New component: [ml:332{166},l:330{165}]"Microsoft-Hyper-V-Drivers-VmSwitch-Common, Culture=neutral, Version=6.3.9600.16384, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}
Installer name: [6]"Events"
2014-01-27 17:00:05, Info CSI 000000a5 Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:5f4cee22ab1bcf015d00000080059405} pathid: {l:16 b:5f4cee22ab1bcf015e00000080059405} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-d..ers-vmswitch-common_31bf3856ad364e35_6.3.9600.16384_none_20abdb73d34c8801" pid: 580 starttime: 130353335013267072 (0x01cf1baae4c0d680)
2014-01-27 17:00:05, Info CBS Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Percent progress: 92.
2014-01-27 17:00:05, Info CBS Winlogon: TiCoreOnCreateSession has been called
2014-01-27 17:00:06, Info CSI 000000a6@2014/1/27:22:00:06.065 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};Microsoft-Hyper-V-Drivers-VmSwitch-Common, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;609232us
2014-01-27 17:00:06, Info CSI 000000a7 End executing advanced installer (sequence 162)
Completion status: S_OK
2014-01-27 17:00:06, Info CSI 000000a8 Begin executing advanced installer phase 38 (0x00000026) index 124 (0x000000000000007c) (sequence 163)
Old component: [l:0]""
New component: [ml:318{159},l:316{158}]"Microsoft-Hyper-V-Drivers-VmSwitch, Culture=neutral, Version=6.3.9600.16423, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
Install mode: install
Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
Installer name: [15]"Generic Command"
2014-01-27 17:00:06, Info CSI 000000a9 Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:cd0f3123ab1bcf015f00000080059405} pathid: {l:16 b:cd0f3123ab1bcf016000000080059405} path: [l:226{113}]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.16423_none_5a097ab253e42b0f" pid: 580 starttime: 130353335013267072 (0x01cf1baae4c0d680)
2014-01-27 17:00:06, Info CSI 000000aa Calling generic command executable (sequence 1): [30]"C:\WINDOWS\System32\netcfg.exe"
CmdLine: [51]""C:\WINDOWS\System32\netcfg.exe" -e -c s -i VMS_VSF"
2014-01-27 17:00:06, Info CBS Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Percent progress: 93.
2014-01-27 17:00:06, Info CBS Winlogon: TiCoreOnCreateSession has been called
2014-01-27 17:00:06, Info CSI 000000ab Performing 1 operations; 1 are not lock/unlock and follow:
(0) LockComponentPath (10): flags: 0 comp: {l:16 b:baf6b823ab1bcf016100000080059405} pathid: {l:16 b:baf6b823ab1bcf016200000080059405} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.3.9600.16384_none_cd3183f2deb856d2" pid: 580 starttime: 130353335013267072 (0x01cf1baae4c0d680)
2014-01-27 17:00:07, Info CSI 000000ac Creating NT transaction (seq 3), objectname [6]"(null)"
2014-01-27 17:00:07, Info CSI 000000ad Created NT transaction (seq 3) result 0x00000000, handle @0x3fc
2014-01-27 17:00:07, Info CSI 000000ae@2014/1/27:22:00:07.049 Beginning NT transaction commit...
2014-01-27 17:00:07, Info CSI 000000af@2014/1/27:22:00:07.205 CSI perf trace:
CSIPERF:TXCOMMIT;208698
2014-01-27 17:00:07, Error CSI 000000b0 (F) Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK
Process exit code 515 (0x00000203) resulted in success? FALSE
Process output: [l:74 [74]"Trying to install VMS_VSF ...
... failed. Error code: 0x800f0203.
"][gle=0x80004005]
2014-01-27 17:00:07, Info CSI 000000b1 Calling generic command executable (sequence 2): [30]"C:\WINDOWS\System32\netcfg.exe"
CmdLine: [50]""C:\WINDOWS\System32\netcfg.exe" -e -c p -i VMS_PP"
2014-01-27 17:00:08, Error CSI 000000b2 (F) Done with generic command 2; CreateProcess returned 0, CPAW returned S_OK
Process exit code 256 (0x00000100) resulted in success? FALSE
Process output: [l:73 [73]"Trying to install VMS_PP ...
... failed. Error code: 0x800f0100.
"][gle=0x80004005]
2014-01-27 17:00:08, Info CSI 000000b3 Calling generic command executable (sequence 3): [30]"C:\WINDOWS\System32\netcfg.exe"
CmdLine: [51]""C:\WINDOWS\System32\netcfg.exe" -e -c p -i VMS_VSP"
2014-01-27 17:00:08, Info CSI 000000b4 Done with generic command 3; CreateProcess returned 0, CPAW returned S_OK
Process exit code 0 resulted in success? TRUE
Note:
"Trying to install VMS_VSF ...
... failed. Error code: 0x800f0203.
When I restart after enabling the feature, I get "Could not complete the updates" and everything rolls back.
I've tried to search for a solution, I've done the DISM /RestoreHealth, to no avail. What could be causing this?

After making the BIOS changes the box needs to be cold booted.
Some BIOS options will not become available without a cold boot. And with laptops this can equal pulling the battery.
Also, don't miss updating the BIOS.
And last, ensure that the flavor of the chipset that you have really does support the feature. As there are cases where the motherboard supports it, or the BIOS allows enabling it, but the chipset does not actually have it.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Vista problem and error createding users.

Hi All. About 4 weeks back I took on a task to install Leopard server in a small office. 5 macs all running leopard and one dell running Vista home basic.
The server is a brand new Mini with 4 Gigs of Ram and the 320 Gig HD. Storage is on a 2T external box.
Installation was a nightmare. I had to install via Target disk as the Mini was too new to boot from the Leopard DVD (10.5.4) then apply the updates while running the server on the host mac using the mini's HD as the startup drive. It took about 4 goes to get it all up and running.
I set up the users and all's well - except for the dell. It can access the shares and read but cannot write, despite having the same priviledges as the rest of the group. What puzzles me (I know too little about windows and even less about vista) is that while the macs all presented a log-in/password box when they first connected, the dell just went straight to the shares. I cannot find a way of making the dell authenticate. Have I done something wrong or is it Vista home Basic that is the culprit.
Next issue, I cannot get a shared iCal to work (but the wiki calendar works brilliantly) as I keep getting told (this is me the admin) that I don't have permission!
Third issue (and this is worrying me), while testing with the dell I created another user with a new name just to see if it was the original settings that were at fault - but - I couldn't. Everytime I tried to create a new user I get an error message -
"User creation failed. The server reported the error '-14120' while trying to create the user"
It doesn't matter what I do I cannot create another user.
I'd really appreciate some help here.
Finally, (it's not a problem - yet) I have to set it up so that all the users can log in from home to access the shares - and that includes the dell.

Hi David, I'm back again.
The problem I'm having with the new user error may be hidden in this short section from the log:
Also, one of the users (who has been perfectly OK) is now getting a Kerberos log-in error and can no longer write to the shares.
LOG:
Sep 28 13:33:57 MuseMini imap[81400]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)
Sep 28 13:33:57 MuseMini imap[81400]: badlogin: [172.16.1.36] GSSAPI [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)]
Sep 28 13:36:06 MuseMini ctl_cyrusdb[81445]: checkpointing cyrus databases
Sep 28 13:36:06 MuseMini ctl_cyrusdb[81445]: done checkpointing cyrus databases
Sep 28 13:36:22 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:36:22 MuseMini servermgrd[61]: servermgr_accounts: got error -14120 trying to write config record
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini servermgrd[61]: DirectoryService crash detected, reauthorizing node
Sep 28 13:38:43 MuseMini Server Preferences[80311]: XSAdminQueueController: gotServerError: -14120 forTransaction: <XSAdminTransaction: 0x1711f980>
Sep 28 13:38:43 MuseMini servermgrd[61]: servermgr_accounts: got error -14098 trying to log to local LDAP node
Sep 28 13:38:43 MuseMini Server Preferences[80311]: Error creating user: {\n command = createUser;\n error = "-14120";\n}
Sep 28 13:38:57 MuseMini imap[81506]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)
Sep 28 13:38:57 MuseMini imap[81506]: badlogin: [172.16.1.36] GSSAPI [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)]
Sep 28 13:38:57 MuseMini imap[81509]: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired name)
Sep 28 13:38:57 MuseMini imap[81509]: badlogin: [172.16.1.36] GSSAPI [SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No principal in keytab matches desired
It looks to me as though I may have to go through the entire install again - and I really don't want to do that.
Help!

Error while Installation: Windows Setup failed to install (...) while offline servicing the image

Hello,
I'm facing some issues Use Log Files to At setuperr.log
2015-03-13 11:43:00, Error 2015-03-13 11:43:00, Error 2015-03-13 11:43:18, Error 2015-03-13 11:43:18, Error 2015-03-13 11:43:18, Error At cbs_unattend.log
2015-03-13 11:41:50, Info 2015-03-13 11:41:50, Info 2015-03-13 11:42:01, Info 2015-03-13 11:42:01, Info 2015-03-13 11:42:01, Info 2015-03-13 11:42:01, Info 2015-03-13 11:42:15, Info 2015-03-13 11:42:58, Info 2015-03-13 11:43:00, Info 2015-03-13 11:43:00, Error 2015-03-13 11:43:02, Error 2015-03-13 11:43:02, Error 2015-03-13 11:43:02, Error 2015-03-13 11:43:02, Error 2015-03-13 11:43:02, Error 2015-03-13 11:43:02, Error 2015-03-13 11:43:02, Error 2015-03-13 11:43:02, Info I've googled for Could anyone please I've uploaded cbs_unattend.log http://www.filedropper.com http://www.filedropper.com/setupact while installing an image from configuration file of Windows Embedded 8 Standard. I get an error message which I've tried to indentify using this guide
Diagnose Image Builder Wizard Installation Problems (Standard 8). I haven't succeeded at all. The errors I have are the following:
CBS Failed to process single phase execution. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
CBS Failed to perform operation. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
[0x060766] IBS ApplyUnattendFileUsingDism: DISM returned error exit code 2
[0x06076d] IBS ApplyUnattendFileUsingDism: See DISM log file [D:\$WINDOWS.~BT\Sources\Panther\cbs_unattend.log] for more details.
[0x060768] IBS ApplyUnattendFileUsingDism: Failed to use DISM to install modules and apply settings. Error code = 0x80070002
DISM Embedded Manager: PID=460 TID=544 Success coping module from "C:\AutoUnattend_Files\offlineServicing\vvvv_45beta33.7~0000000000000000~amd64~~1.0.0.0.emd" to "D:\Windows\servicing\Modules\PendingInstall\vvvv_45beta33.7~0000000000000000~amd64~~1.0.0.0.emd" - ModuleInstaller::CopyForPostboot
DISM DISM Package Manager: PID=460 TID=544 CBS session options=0x0! - CDISMPackageManager::Internal_Finalize
DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
DISM DISM Package Manager: PID=460 TID=384 Error in operation: (null) (CBS HRESULT=0x80070002) - CCbsConUIHandler::Error
DISM DISM Package Manager: PID=460 TID=544 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070002)
DISM DISM Package Manager: PID=460 TID=544 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070002)
DISM Embedded Manager: PID=460 TID=544 Failed to process package installation(s) - ModuleInstaller::InstallModules(hr:0x80070002)
DISM Embedded Manager: PID=460 TID=544 Failed to install modules - CEmbeddedManager::Apply(hr:0x80070002)
DISM DISM Unattend Manager: PID=460 TID=544 Error applying unattend for provider: Embedded Manager - CUnattendManager::Apply(hr:0x80070002)
DISM DISM Unattend Manager: PID=460 TID=544 base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:674 - CUnattendManager::InternalExecuteCmdLine(hr:0x80070002)
DISM DISM Unattend Manager: PID=460 TID=544 base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:623 - CUnattendManager::ExecuteCmdLine(hr:0x80070002)
DISM DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80070002
DISM DISM Provider Store: PID=460 TID=544 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
them and I've read that the 0x80070002 may be related to updates, but nothing particular about the other.
tell me what can be happening?
and setupact.log in case they are helpful.
/cbsunattend

It's strange, because I can install that package, and all the other custom ones without error if updates, security updates and hotfixes are not included. It must be one of those packages which is causing the install to fail. I tried to install updates manually
once I deployed the image but after the updates some of my custom applications didn't work well.
All of this just happening on the intel board, not the amd one.

DISM / SFC

dism / sfc do not work.
sfc returns the following, Windows Resource Protection could not perform the requested operation. (stops at 2%)
dism returns Error 0x800f081f.
Any info and when may be resolved.

Additionally, not using the /source and /limitaccess switches will allow Windows to use Windows Update as a repair source, which would work in the scenario where you have corruption related to payload that isn't in the installation media (install.wim).
You can still use the install.wim file as your repair source (network share, flashdrive, etc...), but it would need to be continually updated with the same updates that your PCs have by using the DISM command. Just adding this info, since I'm not
sure which scenario is more applicable to your environment.

Error values

Hi!
I'm working on an C++ application that calls java web start with the -wait option. I need to return a error value if the page can't be loaded. Is there any way to do that? How can I catch the error value?
Thanks.

if you use 1.5.0 or later, and you invoke "javaws -silent ..." you should always get return value of -1 if app cannot be started, or if main of app throws an exception.
However, you can't really run an app in silent mode (unless it is really a console app and dosn't show any gui)
If you run just "javaws -wait <url>" it will usually double launch, so it will only wait for the first invocation of java to return, which will succeded. to prevent a double launch, dowload the jnlp file youself and run "javaws -wait <filename>".
In this case any problem encountered will cause a launch error dialog (since it's not silent) and -1 treturn will only come back after the user has dismisses the error dialog.
If you want "almost silent" such that program can use gui, but not show error dialogs, you need to wait till version 6.0, which has the "-quiet" option.
/Andy

Component store corrupt after w8.1 spring update

hi,
I have applied windows 8.1 pro spring update without problems. attempted to do cleanup with
dism /online /cleanup-image /startcomponentcleanup
the system comes up with messages showing component store is corrupt , error : 14098.     I run
dism /online /cleanup-image /scanhealth               which answers component store is repairable. so I run
dism /online /cleanup-image /restorehealth          and after 40% complete the result is
    'either the repair source cannot be found or the component store cannot be repaired' error: 0x800f081f . the log at
      \windows\logs\dism\dism.log   shows some text written is what I think is Japanese alphabet.
I do a system image restore disk reverting windows to its state in march, check the component store and it is healthy.
  I do the w8.1 pro spring update again.
   this puts the component store into the situation above.
  I can do a clean intstall when w8.1 pro iso is available. any ideas?
  regards.

# as an HRESULT: Severity: FAILURE (1), Facility: 0xf, Code 0x81f
# for hex 0x81f / decimal 2079 :
ecIFSDupFile ec.h
Hi,
This error code can occur when an alternative installation source is specified and one of the following conditions is true:
The location that is specified by the path does not contain the files that are required to install the feature.
The user who tries to install the feature does not have at least READ access to the location and to the files.
The set of installation files is corrupted, incomplete, or invalid for the version of Windows that you are running.
I suggest that you upload the dism.log so that we can help you analyze them.
Regards,
Kelvin Xu
TechNet Community Support

Sfc /scannow - Cannot repair member file

I ran sfc /scannow and then filtered the results to a file. There are several errors that were flagged that could not be repaired. They seem to be related to an update "Package_83_for_KB2769165".
What can I do to fix the files?
2013-01-14 15:42:22, Info CSI 0000030d [SR] Verifying 100 (0x00000064) components
2013-01-14 15:42:22, Info CSI 0000030e [SR] Beginning Verify and Repair transaction
2013-01-14 15:42:27, Info CSI 0000030f Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2013-01-14 15:42:27, Info CSI 00000310 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-01-14 15:42:46, Info CSI 00000311 Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2013-01-14 15:42:46, Info CSI 00000312 [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-01-14 15:42:46, Info CSI 00000313 [SR] This component was referenced by [l:160{80}]"Package_83_for_KB2769165~31bf3856ad364e35~x86~~6.2.1.0.2769165-10628_neutral_GDR"
2013-01-14 15:42:48, Info CSI 00000314 [SR] Verify complete
2013-01-14 15:42:48, Info CSI 00000315 [SR] Verifying 100 (0x00000064) components
2013-01-14 15:42:48, Info CSI 00000316 [SR] Beginning Verify and Repair transaction
2013-01-14 15:42:52, Info CSI 00000317 [SR] Verify complete
2013-01-14 15:42:52, Info CSI 00000318 [SR] Verifying 100 (0x00000064) components
2013-01-14 15:42:52, Info CSI 00000319 [SR] Beginning Verify and Repair transaction
2013-01-14 15:42:57, Info CSI 0000031a [SR] Verify complete
2013-01-14 15:42:57, Info CSI 0000031b [SR] Verifying 100 (0x00000064) components
2013-01-14 15:42:57, Info CSI 0000031c [SR] Beginning Verify and Repair transaction
2013-01-14 15:43:03, Info CSI 0000031d [SR] Verify complete
2013-01-14 15:43:03, Info CSI 0000031e [SR] Verifying 100 (0x00000064) components
2013-01-14 15:43:03, Info CSI 0000031f [SR] Beginning Verify and Repair transaction
2013-01-14 15:43:17, Info CSI 00000323 [SR] Verify complete
2013-01-14 15:43:17, Info CSI 00000324 [SR] Verifying 67 (0x00000043) components
2013-01-14 15:43:17, Info CSI 00000325 [SR] Beginning Verify and Repair transaction
2013-01-14 15:43:21, Info CSI 00000326 [SR] Verify complete
2013-01-14 15:43:21, Info CSI 00000327 [SR] Repairing 1 components
2013-01-14 15:43:21, Info CSI 00000328 [SR] Beginning Verify and Repair transaction
2013-01-14 15:43:22, Info CSI 00000329 Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2013-01-14 15:43:22, Info CSI 0000032a [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-01-14 15:43:22, Info CSI 0000032b Hashes for file member \SystemRoot\WinSxS\x86_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_a1af7694d303e9dc\I386\CNBJ2530.DPB do not match actual file [l:34{17}]"I386\CNBJ2530.DPB" :
Found: {l:32 b:4uk9tm5oyYcvbi9VbkRxejcqVHTrvt1WZoWcPIlOeII=} Expected: {l:32 b:n520k714Uu3utHa5JGQ6HQYbZphKhlMWq5pEmfnCDuw=}
2013-01-14 15:43:22, Info CSI 0000032c [SR] Cannot repair member file [l:34{17}]"I386\CNBJ2530.DPB" of prncacla.inf, Version = 6.2.9200.16430, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-01-14 15:43:22, Info CSI 0000032d [SR] This component was referenced by [l:160{80}]"Package_83_for_KB2769165~31bf3856ad364e35~x86~~6.2.1.0.2769165-10628_neutral_GDR"
2013-01-14 15:43:22, Info CSI 0000032e [SR] Repair complete
2013-01-14 15:43:22, Info CSI 0000032f [SR] Committing transaction
2013-01-14 15:43:23, Info CSI 00000334 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

Please run the new DISM command instead:
DISM /Online /Cleanup-Image /RestoreHealth
it can download missing files.
"A programmer is just a tool which converts caffeine into code"
The DISM command doesn't work in an environment that runs Windows Server Update Services, unless you configure the
Specify settings for optional component installation and component repair setting:
http://technet.microsoft.com/en-us/library/hh825020.aspx#BKMK_SetGPO
The default source location is Windows Update. Before configuring this, the output is displayed as below:
C:\Windows\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.16384
Image Version: 6.3.9600.16384
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see
http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
When configuring Specify settings for optional component installation and component repair, select
Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS).
Run the DISM command again and the operation will complete successfully.
or use note pad create a repair.bat file, copy and paste the text, run as admin.
net stop wuauserv
cd %systemroot%\SoftwareDistribution
ren Download Download.old
net start wuauserv
net stop bits
net start bits
net stop cryptsvc
cd %systemroot%\system32
ren catroot2 catroot2old
net start cryptsvc
Then try this again
DISM /Online
/Cleanup-Image
/RestoreHealth
http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_update/dismexe-online-cleanup-image-restore-health-failed/668ef107-5f4c-4959-ba93-76d052452315
Edit: I had the same error code as you not to long ago, the above repairbat fixed that problem.
Little easier then configuring paths and running dism. I have fixed the error doing it that way too. Below is the link how to my how to. check my post
http://social.technet.microsoft.com/Forums/windows/en-US/d126a392-1491-4371-962c-1d1269806aff/win-81-pro-dism-online-cleanupimage-restorehealth-returns-error-14098?forum=w8itprogeneral#f2ae2d58-aad6-446a-a648-b709ec87b5d2

Windows 8.1 keeps locking up after about 1hr of use.

For the past two days, my computer locks up after about an hour of use. It doesn't always freeze, sometimes it just moves incredibly slow. Every thing I try to click takes at least 5-10 minutes to load. My computerr is ASUS r500v, intel core i7,8gb memory,
1tb hdd.
At first, the computer would freeze in Google Chrome saying "waiting for cache" and after cleaning cache and trouble shooting for hours, I decided to uninstall google chrome. I am now using firefox. I try to run virus scans, but my
computer won't work long enough for that. When I do run one though, it gets 4 issues (i've cleaned two of them)
Ran "sfc /scannow" and it told me that it fixed some but not all of the issues. then ran "dism /startcomponentcleanup successfully. ran dism /restorehealth and it said "could not download source files"
Can anyone help me?

Hi,
For Windows 8.1 freezes, have we checked this KB article?
Windows 8.1, Windows 8 or Windows 7 hangs or freezes
For the dism repair, please refer this KB article, if we have an install disk available:
Fix Windows corruption errors by using the DISM or System Update Readiness tool
DISM.exe /Online /Cleanup-image /Restorehealth
Important When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions. However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or
use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. To do this, run the following command instead:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
Note Replace the C:\RepairSource\Windows placeholder with the location of your repair source. For more information about using the DISM tool to repair Windows, reference
Repair a Windows Image
Please follow the steps listed in the KB article.
Best regards
Michael Shao
TechNet Community Support

Problem updating to windows 8.1

recently i was told to update to windows 8.1 due to the 'IRQL...' bluescreen driver error and am supposed to proceed further. but i found it is showing "something happened and windows cant install...." and even my windows update are supposed
to be updated but though i try many times updating by downloading they are not getting done. so please tell me how to proceed further??

Hi,
Have you tried the SFC command?
Use the System File Checker tool to repair missing or corrupted system files
We might also take a try with the DISM restorehealth.
Fix Windows corruption errors by using the DISM or System Update Readiness tool
If the above won't help, please consider to do an upgrade install of Windows 8
Please try to fix the error first, and then take the update.
Best regards
Michael Shao
TechNet Community Support

DISM restorehealth error 14098

Similar Messages

Maybe you are looking for