WinPE 3.1 issue adding driver using DISM
I have a USB capable of booting with WinPE3.1 (win 7)
To this winPE3.1 wim image, I tried injecting a driver using :
dism.exe /image:C:\WinPEMount /add-driver /driver:< path
to driver .inf file >
The adding of driver was successfull, But on booting this image, the driver is not working (I get errors in my program when I use the driver functionalities)
After booting, I installed the same driver using devcon.exe, it works fine (My program is able to use the driver functionalities).
I dont want to have a script install the drivers every time when it boots, I would like to add the driver to the image offline.
What is the difference between these two processes and what could have gone wrong in the first case?
Edit: I couldn't find a correct section for this question hence posted here. Moderators please move to appropriate section if you can.
Thanks,
Basavesh
Hi,
What is the error message? To add a drive to an offline winPE image , please make sure to follow steps in the links below:
Add Device Drivers on an Offline Windows PE Image
http://technet.microsoft.com/en-us/library/dd799289(v=ws.10).aspx
WinPE: Add drivers
http://technet.microsoft.com/en-in/library/dn613857.aspx
After you add the driver, you can first verify the driver
Dism /Get-Drivers
You must unmount the image and commit the change after you have modified it. such as:
dism /unmount-wim /commit
If issue persists, then please check if the following files exist, upload them to OneDrive for further analysis:
%windir%\Panther\CBS.log
%windir%\inf\Setupapi.dev.log
%windir%\inf\Setupapi.offline.log
Yolanda Zhu
TechNet Community Support
Similar Messages
-
Unable to capture C drive using Dism and imageX commands
I am trying to capture C drive using dism command but it did not work, but the same command is capturing E drive. i am using following command.
dism /Capture-Image /ImageFile:E:\image.wim /CaptureDir:C:\ /name:"Image File"
I am getting following error.
Deployment Image Servicing and Management tool
Version: 6.3.9431.0
Error: 32
The process cannot access the file because it is being used by another process.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
An in the log file the error is: DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070020Hi,
As far as I know, Dism command doesn't support hot image backup, that to say, you do need to complete the image backup job at Windows PE enviroment.
The contents of the link below also list the Dism command capture image requirement:
http://technet.microsoft.com/en-us/library/hh825072.aspx
Roger Lu
TechNet Community Support -
0xc0000135 while adding driver packages to boot image
Hi, I am currently having issues adding driver packages to the boot image.
Currently running Server 2008 R2 and have MDT 2013 installed.
Tried searching for the error but no luck. No matter if I choose the specific driver I want to add or if I just start from the beginning it just constantly fails. Does anybody have any clue as to what could be causing it to not accept either from the boot image
created from MDT Deployment Share or even using a generic boot image?Hi,
First make sure you are using the correct version of DISM
Secondly look at this http://social.technet.microsoft.com/Forums/en-US/ff8509ec-0ddd-4ad8-9e53-ecf527a80919/dismexe-is-failing-to-add-drivers-to-a-mounted-image-file?forum=w7itproinstall -
hello Mrs/Mr
I have some difference on "installing win2k12 server" by winpe(8.1) way.
the case is the following Win2k12 R2 x64 version
step1:
dism /Apply-Image /imagefile:d:\split_install.swm /swmfile:d:\split_install*.swm /Index:4 /ApplyDir:u:\
step2:
dism /image:u:\ /Add-Driver /Driver:d:\drivers\ /Recurse
There are no problem on Step2 on installing win2k12 R2 x64 debugcheck or win8/win8.1.
But there are error on Step2 on installing 10005.0.150125-0130.WINMAIN_PRS_SERVER_OEMRET_X64FRE_EN-US.
the error info is list here
2015-03-04 14:32:17, Info DISM DISM WIM Provider: PID=1932 TID=1988 [u:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2015-03-04 14:32:17, Info DISM DISM VHD Provider: PID=1932 TID=1988 [u:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2015-03-04 14:32:17, Info DISM DISM Provider Store: PID=1932 TID=1988 Getting Provider VHDManager - CDISMProviderStore::GetProvider
2015-03-04 14:32:17, Info DISM DISM Provider Store: PID=1932 TID=1988 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-03-04 14:32:17, Info DISM DISM VHD Provider: PID=1932 TID=1988 [u:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
Can you help me how to resolve this problem?
(I want to add drivers after windows applied instead of adding driver into install.wim because I need detect the onboard device to add driver into windows)
thanks with regards!
feihu QinSorry I didn't respond right away. Got busy on other matters and this issue slipped my mine. Developements have happened...
On coming back to this project, the HD on my laptop died (development comp). Never had any display issues on this machine (was previously posting about issue on computer where app will be run from, where issue still exists). After re-installing everything on my new HD, I'm now experiencing this problem on my development laptop as well.
I'm using an IBM Thinkpad T30 (P4-M, 2.0GHz, 256MB, ATI 7500 Mobility). So it used to display fine on this machine, now it doesn't, and I'm experiencing the same symptoms: grainy display from what appears to be a lower resolution colour palette (maybe 256).
Here too, this is only an issue within the development environment. The startup Labview splash screen looks fine (again LV7.1), the blue bar along the top of all windows transitions from the darker shade of blue to the lighter shade, properly. This issue is on the toolbar and in the developement area within Labview only.
It's weird how this appears to just come or just go. I don't remember who, but somebody here mentioned how their problem just stopped as suddenly as it started. And as this is localized to LV, I'm inclined to think this is not the video card, but perhaps some file/driver/dll that perhaps gets modified/updated without direct visibility. I briefly had this issue aswell on an older Toshiba laptop about a year ago, but it eventually "fixed" itself aswell (don't remember model/specs of older Toshiba).
Anymore help and research into the issue will be most appreciated.
Sean -
JDBC-ORACLE CONNECTIVITY ISSUE WITYH OCI8 DRIVER using oracle 11g client..
JDBC-ORACLE CONNECTIVITY ISSUE WITYH OCI8 DRIVER using oracle 11g client..
I am getting below error when i m trying to access oracle db using oracle 11g client. It works with earlier oracle client versions. how do i resolve this. is there any issue with version of ojdbc6.jar that i am using??? I cant use thin driver since its an old application for which i dont have source files.
Apr 6, 2013 1:00:59 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:992)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:262)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at PettyCash.SysDate.getSysSubSys(SysDate.java:232)
at org.apache.jsp.PettyCash.index_jsp._jspService(org.apache.jsp.PettyCash.index_jsp:186)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Code is as follow for reference
import oracle.jdbc.driver.*;
DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
conn = DriverManager.getConnection ("jdbc:oracle:oci8:@" + database,db_user, db_pass);
eNVIRONMENT VARIABLES set are as follows:
classpath
C:\Program Files\apache-tomcat-5.5.12\common\lib\servlet-api.jar;C:\Program Files\apache-tomcat-5.5.12\webapps\ROOT\WEB-INF\lib\classes12.jar;C:\Program Files\apache-tomcat-5.5.12\webapps\ROOT\WEB-INF\lib\ojdbc6.jar;
JAVA_HOME
C:\Program Files\Java\jdk1.5.0_04
PATH
C:\Program Files\Java\jdk1.5.0_04\bin
ORACLE_HOME
D:\Oracle11\product\11.2.0\client_1\BINApr 8, 2013 5:24:06 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at org.apache.jsp.abc.index_jsp._jspService(org.apache.jsp.abc.index_jsp:280)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:868)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:663)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595) -
I recently started experiencing memory issues with my iMac due to One Drive using up to 5GB of my iMac memory (total of 8GB). Every time I start up my iMac Activity Monitor shows One Drive uses around 4-5Gb of the internal memory for no reason. Previously Onde Drive seemed to work fine, it's only since about 2 weeks I notice this. It's really annoying as the iMac freezes up regulalrly and I need One Drive to synchronise my files across different devices.
Has anyone experienced this too and are there any known fixes?Yes this is happening to me too, since the last upgrade. Eventually MacOS starts insisting I "Force Quit" all my applications as I have run out of application memory.
OneDrive doesn't appear in that list because it's not an application... but Activity Monotor clearly shows it's the culprit, taking up 5GB+ of RAM.
I've raised the issue on Microsoft's forums:
http://answers.microsoft.com/en-us/onedrive/forum/sdperformance-sdother/onedrive -for-macos-memory-leak/fe04cf60-949f-47b6-b886-10539b5c5cc3?tm=1397636232934 -
How to install MSFT application security updates in cab file format using DISM
Hi,
I tried to install security updates for MS Office which are cab files like any other windows security updates cab file. It is giving an error called "file not found". But other windows security updates cab files are installing fine without any error.
I tried to install these updates manually using DISM on commandline. It is not installing. I even tried using pkgmgr.exe, but that is not working either. I looked at DISM logs which is saying it failed opening the cab file. I tried different other commandline
options of DISM to install this, but nothing else is suitable for a cab file install.
Does anyone know how to install a cab file for application security updates via DISM.exe or other MSFT commandline tools?
Thanks,
ANSA
DISM log:
=======
2015-02-25 14:42:59, Info DISM PID=4916 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2015-02-25 14:42:59, Info DISM PID=4916 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Failed to get and initialize the PE Provider. Continuing by assuming that
it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Manager: PID=4916 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM.EXE:
2015-02-25 14:42:59, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2015-02-25 14:42:59, Info DISM DISM.EXE:
2015-02-25 14:42:59, Info DISM DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2015-02-25 14:42:59, Info DISM DISM.EXE: Executing command line: "C:\Windows\System32\Dism.exe" /online /add-package /packagepath:"C:\ProgramData\Application
Data\Autonomic\ANSA Patch Manager\_Installs\mscomctlocx-x-none_8699d53bec82460b948612f4f35d2f6a0ad018f4.cab" /ignorecheck /norestart
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=4916 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Manager: PID=4916 Successfully loaded the ImageSession at "C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B"
- CDISMManager::LoadImageSession
2015-02-25 14:42:59, Info DISM DISM Image Session: PID=11836 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\OSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\OSProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM OS Provider: PID=11836 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM OS Provider: PID=11836 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\LogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\LogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Getting Provider OSServices - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\PEProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Warning DISM DISM Provider Store: PID=11836 Failed to Load the provider: C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\PEProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Failed to get and initialize the PE Provider. Continuing by assuming that
it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Manager: PID=4916 Image session successfully loaded from the temporary location: C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B
- CDISMManager::CreateImageSession
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Getting Provider OSServices - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info DISM DISM.EXE: Target image information: OS Version=6.1.7601.17592, Image architecture=amd64
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\CbsProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\CbsProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2015-02-25 14:42:59, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 CBS is being initialized for online use. More information about CBS actions can
be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\MsiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\MsiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\IntlProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\IntlProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\DmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\DmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info CSI 00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_OBJECT_PATH_NOT_FOUND
2015-02-25 14:42:59, Info CSI 00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\pkgmgr.exe"
: got STATUS_SUCCESS
2015-02-25 14:42:59, Info DISM DISM OS Provider: PID=11836 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2015-02-25 14:42:59, Info DISM DISM Driver Manager: PID=11836 Further logs for driver related operations can be found in the target operating
system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\UnattendProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\UnattendProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\SmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\SmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has not previously been encountered. Attempting to initialize the
provider. - CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Loading Provider from location C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\TransmogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Connecting to the provider located at C:\Windows\TEMP\7D6E845E-B72B-4EAC-B1F4-E853B46FBB3B\TransmogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2015-02-25 14:42:59, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2015-02-25 14:42:59, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2015-02-25 14:42:59, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2015-02-25 14:42:59, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2015-02-25 14:42:59, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2015-02-25 14:42:59, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2015-02-25 14:42:59, Info DISM DISM Transmog Provider: PID=11836 Current image session is [ONLINE] - CTransmogManager::GetMode
2015-02-25 14:42:59, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Processing the top level command token(add-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Encountered the option "packagepath" with value "C:\ProgramData\Application
Data\Autonomic\ANSA Patch Manager\_Installs\mscomctlocx-x-none_8699d53bec82460b948612f4f35d2f6a0ad018f4.cab" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2015-02-25 14:42:59, Error DISM DISM Package Manager: PID=11836 Failed opening package. - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070002)
2015-02-25 14:42:59, Error DISM DISM Package Manager: PID=11836 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x80070002)
2015-02-25 14:42:59, Error DISM DISM Package Manager: PID=11836 Failed to open the package at location: "C:\ProgramData\Application Data\Autonomic\ANSA
Patch Manager\_Installs\mscomctlocx-x-none_8699d53bec82460b948612f4f35d2f6a0ad018f4.cab" - CPackageManagerCLIHandler::ProcessPackagePath(hr:0x80070002)
2015-02-25 14:42:59, Error DISM DISM Package Manager: PID=11836 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Further logs for online package and feature related operations can be found at
%WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2015-02-25 14:42:59, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002
2015-02-25 14:42:59, Info DISM DISM Image Session: PID=11836 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Package Manager: PID=11836 Finalizing CBS core. - CDISMPackageManager::Finalize
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Found the OSServices. Waiting to finalize it until all other providers are
unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Found the PE Provider. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Found the OSServices. Waiting to finalize it until all other providers are
unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:42:59, Info DISM DISM Provider Store: PID=11836 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:43:00, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2015-02-25 14:43:00, Info DISM DISM.EXE:
2015-02-25 14:43:00, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2015-02-25 14:43:00, Info DISM DISM.EXE:
2015-02-25 14:43:00, Info DISM DISM Image Session: PID=4916 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2015-02-25 14:43:00, Info DISM DISM Provider Store: PID=4916 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2015-02-25 14:43:00, Info DISM DISM Provider Store: PID=4916 Found the OSServices. Waiting to finalize it until all other providers are
unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-02-25 14:43:00, Info DISM DISM Provider Store: PID=4916 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProviderYou need to extract and install it - Refer this link
http://blogs.technet.com/b/askcore/archive/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-within-windows.aspx
Regards Chen V [MCTS SharePoint 2010] -
How do I restore a failed external hard drive using Time Machine?
I have an external hard drive connected to my iMac that is being backed up with Time Machine. I just realized that should it one day fail and no longer appear as a connected device, I'm not sure how to restore its data to another external drive. When I disconnected the external hard drive (to mimic a drive crash) and entered Time Machine to see if I could verify that the external hard drive was, in fact, being backed up - I didn't know where to find it. Under the Today (Now) information, I didn't expect to see it there as it was no longer connected to the machine. But when I went back a few days, I expected to see its backup appear in the Sidebar. But no!
So - how do I restore a failed external hard drive using Time Machine?
Searches for this information on Google yielded "iffy" results. I'm hoping someone here is able to offer some clear steps to follow. Perhaps I'm missing something silly. Thank you very much!I came across this discussion after encountering the same problem. Since my internal HD was cose to full I added an additional external HD to my setup. I moved my iPhoto files to an external HD and backed both this external HD and my internal HD up with Time Machine to another external HD. So far the theory. When I wanted to test if this setup worked I noticed that I could only see my iPhoto libraries on the external HD in Time Machine when the external HD was connected to my computer, but not if I turned it off. This led me to search for a solution on the Apple Support Communities discussion board.
The suggestions made Kappy seem right, at least in my experience, in that my Time Machine simply did not back up the external HD until I followed the steps he suggested above. These were the following:
"So, if you want it backed up then here's what you need to do:
1. In Time Machine preferences remove the external drive from the Exclude list.
2. Verify that it is now included with your other drive in the backup list.
3. Do a Backup Now to create a new backup of the external drive."
After doing this, my external HD showed up in the Backups.backupd as a seperate folder. I could clearly see the Time Machine back-up for my internal HD and my external HD. In addition, in Time Machine itself I was able to find the external harddrive by clicking on my own computers name under "Devices". I hope my experience helps to resolve your issue as this discussion board has helped me resolve mine (which I believe to be very similar).
Cheers! -
How to backup external hard drive to another external hard drive using time machine ?
Hello,
i have an external hard drive which i store all my drum samples and sound library on and files are contantly changing, adding new sounds, deleting old ones etc ..
So my method of back up as of now is to just copy all the edited files and click and drag to the back up disk.
Now, my question is, how do i back up my external hard drive to another external hard drive using time machine ? I read somewhere that you can do this, i cant find the post however. It would be nice to automate the back up process rather than manually finding the files to copy over.
Thanks in advance !The question you pose is conditional, in that you should have more than an exact
capacity replacement for a clone, if the drive you are going from (or one going to)
has insufficient free space and that has a bootable clone on the drive; any space
tied up in a partition for Time Machine backup, takes away from the running space
if you should need to run the computer from a clone on the external HDD's other
partition.... Better to have a good capacity of additional reserve unused free space.
Be sure any clone copy that you hope to use as a re-close, that each in turn is tested
after a clone operation. Also consider using each running system's Disk utility and
have First Aid 'repair disk permissions'. Preparation of a new drive or even an old
drive that may have questionable artifacts or errors on it, should be reformatted. To
even go as far as Secure Erase (overwrite) at least one-pass before reformatting it
again, could help.
However, I'm not sure if the drives and situation you are looking at would necessarily
be a good match. It could work, but you'd need a reasonable size partition or hard
disk drive for a system. Snow Leopard and all its associated applications, can do
OK in a 100GB HDD. (My computers have more storage capacity than is used; so
for mine to have 60% free space, is good.) Virtual Memory is drive space used by
OS X, that can be a substantial amount for swap and temp files. Some applications
make duplicates of works-in-progress, for each change in an open file; that adds up.
{This question (& my reply) should've been in their own thread & not at the end
of one that is nearly three months old, + marked 'solved' by the original poster.}
So I guess I don't have a direct answer to your question; having just returned from
a few hundred miles and automobile issues, too. I'm not really thinking on-topic...
The clone should be on its own separate drive, and up to 3TB drive dedicated to
Time Machine may be overkill, however that software will consume old backups first
when it uses up all the space. Or usually that is what happens in TM backups. If
that isn't happening, there may an issue in how Time Machine is set up.
Good luck & happy computing! -
Hi, I was told in another of the forums that my issue
is best suited for the TechNet audience. Previously, I posted it here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/how-to-include-a-kb-update-into-a-wim-in-order-to/e7015076-b4a9-4862-a73b-6c58b4c82461?tm=1409598696763
I've been struggling to fix a corrupted file.
Context: I feel that something is not right with the computer, so I started poking around.
I used "sfc /scannow" from an elevated command prompt and the result was:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log <var style="border:0px;margin:0px;padding:0px;vertical-align:top;-webkit-font-smoothing:antialiased;">%WinDir%</var>\Logs\CBS\CBS.log.
I looked in the log. This message appears 4 times:
Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate",
TypeName neutral, PublicKey neutral in the store, hash mismatch
There is also the following message:
This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"
I'm not positive what to do next, but I have been led to believe the problem is that Flash files in version 6.3.9600.16407 are corrupted, that I need to find which KB updates Flash to this version, download the file, add it to a new WIM, and point
to it when using DISM. I'm not positive this is correct, but it was suggested.
I downloaded the KB update: kb2889543, but I do not know how to add it to a new WIM or what the repercussions of doing so will be (e.g. Will I lose everything and have to restore my documents, etc from my external drive by doing this?).
So, the question is: How can I include a KB Update into a WIM and tell me what the result will be when once I do and point to it when using DISM?
Secondarily, if this is a bad way to move forward with the issue, would some kind soul offer sage advise on how to move forward with resolving the original issue?Hi TTQSTTQS,
As you mentioned in the answers forum, when run the command DISM /Online /Cleanup-Image /RestoreHealth, we received the error message “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”.
When run the command Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows /LimitAccess, we met the same error message.
I think there are some mistakes in the source setting, so we meet the same error messages.
As I mentioned in the last reply, we need a mounted image as a repair source, and then use this path.
We need to configure a Windows repair source. Please refer to the following article.
http://technet.microsoft.com/en-us/library/hh825020.aspx
Please refer to the following steps to set the source image.
1. Assign Drive Letters to Partitions by Windows PE.
2. Capture Partition Images using DISM
For more information, please refer to the following article.
http://technet.microsoft.com/en-us/library/hh825072.aspx
Then, we could try the command Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows /LimitAccess.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support -
Hi,
We capture and modify W7 Ent and Pro OS images on a regular base by using DISM to add drivers for example. Until now we never had a problem because we always had images which only had 1 OS volume captured. DISM works fine to mount the image to a mount
folder, add drivers, and save the changes in the image.
However now we encounter an issue when doing the same actions on an image where the \Windows folder was located on the C:\ volume and \programdata and \users folders where redirected to a D:\ volume.
When mounting the C:\ volume image (including everything except \programdata and \users folders) the error we receive when trying to add or get drivers is:
Error 3 - the \Windows folder is not a valid Windows directory.
The DISM.Log file show right before this error that the remote registry could not be contacted.
This is caused I think because the registry files are located on the \Users folder, but since this folder is not captured in the image (located on another volume during capture) it cannot find the registry.
My question is: how can we resolve this?
What we have now is 1 WIM file where index1 is the OS (C:\ volume) and index2 is the \ProgramData and \Users folders (D:\ volume). Probably the way of capturing the image and redirecting programdata/users is not done in a correct way...
Note: the image index1 and index2 restore works fine - the unattended.xml contains also redirection to the folders paths for \programdata and \users...
Any help or advice would greatly be appreciated!
Thx.
Steve
Wkr, SteveHi Steve,
You can be right that DISM don’t support the scenario that User profile and System are in the separated volumes.
As a workaround, we should use the defaults to put the profile on C: during capture image, and then set the profile path to be on the D: drive after the image deploying.
Please refer to below KB for how to using Sysprep to redirect profiles’ locations.
Customize the default local user profile when preparing an image of Windows
http://support.microsoft.com/kb/973289/en-hk
Hope these could be helpful.
Kate Li
TechNet Community Support -
Using DISM Cmdlets to upgrade Hyper-V Integration Components
Hi guys,
I'm using the Deployment Imaging Servicing Management (DISM) Cmdlets to programmatically upgrade Hyper-V integration components as VMs move about my environment. My code works fine, but I have a little issue:
I'm using a call to 'Add-WindowsPackage' to slipstream in the CAB package in. This works, but sometimes 2008 R2 VMs will immediately boot into the system recovery console -seemingly for no reason. This never happens with 2012 R1 or R2 VMs. This obviously
makes this process not unattended, and I want it to be totally unattended (with reporting to catch stuff).
Does anyone know a.) when this is happening and b.) can I somehow remove this recovery boot flag, is it like the dirty bit?
The weird thing is if I just progress into the recovery console something is changed in the VM and then it will boot just fine. There isn’t a problem with the IC upgrade, but something thinks there is. The logs for the DISM cmdlets are no help.
I don’t have System Centre and wont be using it, FYI.
Cheers!Hi Hob,
Just a little clarification, Please also make sure you had added the right Integration Services package version to WIM file, because each version has a different installation package, it is very important that you select the correct package for the appropriate
OS.
Refer to:
Deploying Hyper-V Integration Services to VMs using Config Manager and DISM:
http://blogs.technet.com/b/manageabilityguys/archive/2013/09/05/deploying-hyper-v-integration-services-to-vms-using-config-manager-and-dism.aspx
If I have any misunderstanding, please feel free to let me know.
Best Regards,
Anna Wang -
How to change the name and description of a wim using DISM
With Imagex we could update the name and description of the wim with on easy command:
imagex /info img_file [img_number or
img_name] [new_name] [new_desc]
e.g.
imagex /info Win7Combined.WIM 1 "Win7(x86)" "Windows 7 x86"
Since the ImageX tool is deprecated in Windows 8 and has been replaced with DISM, can someone explain how to update the name and description with one easy command using DISM like we could with Imagex?It looks like this person had the same issue. Have you seen this
link
It talks about exporting an Index into a new WIM. Which, in a way, would be renaming it. It's really recreating it and you have to give it a name. But it seems to work.
Dustin Estes - MCP | www.dustinestes.com -
When I check my boot SSD drive using Disk Utility under Mavericks, I often get "Incorrect number of extended attributes" errors. But if I boot off an external drive and check the same SSD, no errors are reported.
This happens not just with the SSD in my Mac Mini, but with another SSD in my MacBook (both now running Mavericks). So far as I know, all of the kit I am using is in good order (despite the file corruption reports). So I am beginning to wonder if it could be due to a bug in Mavericks? Both SSD drives have been formatted to MacOS Extended (journaled) format. Should I have used a different format, I wonder?
Has anyone else encountered this issue?
Does anyone have a solution?
Or an explanation that might help my investigation of the issue?
Thanks guys,I understand that the Corsair Force 3 is not one of the SSD drives that are supported on Apple Macs.
I did try downloading and using Trim Enabler, but the error message came up both when it was off and when it was on.
I understand that not everyone thinks Trim Enabler is a good program, though there is a new version out now, so I may give it another try. -
My Time Machine seems to be hanging up (stopping) beforew completion. I'm running Mountain Lion (OS X 10.8.2) on my iMac G5, and I already trouble-shot the external drive used for Time Machine by using Repair on Disk Utilities. So--what gives?
IMac G5 with Mountain Lion.. amazing.. I am pretty sure support for early Intel stopped at ML and support for G5 long before that.
Load the widget and see if you get error message that the TM is ejecting the drive.. before the backup is complete.. that is one of those nice.. features.. Apple has made available in recent updates.. sometimes called bugs.
A1 in here http://pondini.org/TM/Troubleshooting.html
Also look at the other info.. C12 C17 are common issues.
Maybe you are looking for
-
How do I get Microsoft Outlook Web Access to have the same view in Google Chrome as in IE9?
In IE9 I can see a reading pane, just like in a PC view of Outlook. However, I do not know how to get this when using Google Chrome. Can anyone help?
-
Need help with installing ora10gR2 [not enough physical memory]
hey guys, i am trying to install oracle10gR2 on fedora core 4. i installed core 4 with following partitions on a 80gb harddrive. 100 mb /boot 1024 mb swap rest for / the OS is working perfectly fine. but when i try to install ora10g on it it says tha
-
I get a message upon launching iTunes that the registry setting for burning are missing.
I get a message upon launching iTunes that the registry setting for burning CDs and DVDs are missing. I uninstalled and reinstalled iTunes. I didn't touch the registry. iTnes is fine except, of course, I cannot burn songs to CD.
-
I'm attempting to install my newly purchased -from Amazon.com - DVD of PSE 13 for Mac. There is a screen with six sections which is asking me to enter a serial number. The manual states the number, which begins with number 1057, can be found on the
-
We've recently adopted BOBJ/Webi at my company and I find the software to be rather easy to use in some instances and mind-wreckingly hard in others. One roadblock myself and other users are bumping into is calculating work days. A definition of a wo