Windows update requirements for Xerox print drivers on Windows 2003 server

Hello, We are currently deploying a fleet of Xerox MFD's across ~100 locations, and we are running into an issue installing the print drivers on some Windows Server 2003 (32bit) boxes. (both the machine specific driver, as well as the Xerox Global print driver) The print driver installs fine, but no jobs will actually print, and if you try and print a test page, an error "Test page failed to print. Would you like to view the print troubleshooter for assistance?" comes up instantly. We have seem to have narrowed the problem down to a missing Windows update, as if we do all available High Priority and Optional updates, it starts to work fine. Does anybody know specifically which Windows updates are a requirement for the driver?  Our 2003 servers were last fully updated about a year ago, and due to time constraints, if we could just install the Windows updates that are needed it would be a big help. Thank you in advance

When Xerox dropped support for XP, they stopped adding particular files from the driver packs (probably for size reduction) because they were all included by default in every newer OS. If you install this here on any XP/2003 base machines it will work as normal. It is best to install that before the driver install, but I have been mostly lucky to have it work fine days later. YMMV

Similar Messages

  • Windows Update installs older Canon MG4100 drivers in Windows 8/8.1

    When I turn on the MG4120 printer and the printer is already setup for wireless and I have WSD enabled, Windows 8 or 8.1 automatically installs older Canon MG4100 drivers from Windows update.  The same thing happens if I connect the USB printer before installing the Canon software from the website and the same issue also happen in wireless mode.  The version that gets installed by Windows Update is the same version listed in the catalog at http://catalog.update.microsoft.com/v7/site/Search.aspx?q=mg4100.
    Windows 8,Windows 8.1 Drivers,Windows Vista  Drivers (Printers)  8/16/2011  2.50.2.70
    Windows 7  Drivers (Printers)  3/13/2012  18.0.2.31
    Canon, can you please submit the newer printer driver to microsoft Windows Update?

    Hi KeithWeisshar,
    WSD drivers are supplied and supported by Microsoft.  The version numbers and dates are not comparable to the numbers and dates for our drivers.  While WSD will provide you with basic printing capability and some features, to get the most from your printer, I recommend using the drivers found on our website. 
    If you have any other questions, please feel free to Contact Us!
    Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

  • How to update driver for Xerox printer?

    Internal Default driver is FX ApeosPort-III C5500 v3017.104 PS
    I've downloaded Version: 1.70.110 (release date: 29/05/2013) for Mac OS X 10.5-10.8 Print Driver from xerox website
    The file is "Fuji Xerox PS Plug-in Installer.pkg" and double click to install it successfully.
    But how can I choose the latest driver?
    When I try to 'Select Printer Sofftware' from Printer Using, it is no dedicated driver for selecion.
    Any suggestions? Many thanks.

    At printer general page, the driver version is 2.0 before. 
    After I followed your step and add the C5500 driver again, the driver version displays 4.0 now.
    Just confuse how to verify the driver is latest one as I downloaded Version is 1.70.110 (release date: 29/05/2013)

  • Installing additional 32bit printer drivers on Windows Server 2008R2

    Hi,
    I'm trying to add additional printer drivers (32bit) on a 64bit server so that 64bit and 32bit clients can add printers from the print server. I have found several posts about this and none has helped me so far. I found one from GeorgeLawr that
    I copied below:
    I have found the best way to do this is:
    Install the printer/driver for the type of device you are installing on the server, i.e. Xerox printer WCP7765 and driver for this printer (64-bit).
    Share the printer out (optional).
    Test print to make sure it works ok.
    Then from a 32-bit client (must be logged into the client with an account that has admin rights on print server), browse the printer server shares, i.e. go to "Start\Run" and type \\printservername\ then go to "Printers and Faxes" right-click
    and select "Connect" for the required printer and it will say it does not have the required drivers and will ask if you want to install.
    Install the required 32-bit driver and it will install on the print server. You then have to enable this in the printer properties.
    In the print queue window that opens up after you install the queue, go to "Printer\Properties\Sharing\Additional Drivers" and enable the "Intel Windows 2000 or XP" option (note, if you are doing this from a Windows 7/Vista client you might
    have to click "Change Sharing Options" or something, before you can click "Additional Drivers" option).
    And that's it. You should now be able to go to a different 32-bit client and add the printer and print no problem.
    This one gets me closer to an answer; however, on step 5 once it asks for driver path, I direct it to the CD that has the driver and I get a message that states something similar to "this driver is not correct for this version of Windows"
    It's like it's looking for 64bit drivers and the drivers on the CD are 32bit. The printer on the (64bit) server is already installed. I'm on the 32bit client.
    Can somebody help me get this correct?
    Thanks,
    MC

    Hi,
    We can add drivers for client computers running 32-bit or 64-bit versions of Windows.
    To add client printer drivers to the print server
    ==================================
    1. Open Print Management.
    2. In the left pane, click Print Servers, click the applicable print server, and then click Printers.
    3. In the center pane, right-click the printer to which you want to add additional printer drivers, and then click Manage Sharing.
    4. Click Additional Drivers. The Additional Drivers dialog box appears.
    5. Select the check box of the processor architecture for which you want to add drivers.
    For example, if the print server is running an x64-based edition of Windows, select the x86 check box to install 32-bit version printer drivers for client computers running 32-bit versions of Windows.
    6. If the print server does not already have the appropriate printer drivers in its driver store, Windows prompts you for the location of the driver files. Download and extract the appropriate driver files, and then in the dialog box that appears, specify
    the path to the .inf file of the driver.
    Note: You might not be able to extract some printer drivers without installing them. If this is the case, log on to a client computer that uses the same processor architecture as the printer drivers that you want to add to the print server, and install those
    printer drivers. Then use Print Management from the client computer to connect to the print server, and add the additional drivers from the Additional Drivers dialog box. Windows automatically uploads the drivers from the client computer to the print server.
    For details:
    Print driver installation on 32-bit versus 64-bit servers
    http://blogs.technet.com/b/askperf/archive/2010/01/19/print-driver-installation-on-32-bit-versus-64-bit-servers.aspx
    Hope this helps!
    Best Regards
    Elytis Cheng
    Elytis Cheng
    TechNet Community Support

  • XEROX Print Drivers Cause Install Freeze on PowerMac G5

    Tried to do a custom clean install on my dual 2.5 PowerMac by deselecting the drivers for printers I do not have, also deselected the languages and fonts I didn't need. Ran the installer and it froze three times at the same spot – unable to install Xerox print drivers.
    Ran disk utility to verify the disk each time before the install, manually erased the drive as well.
    Had to allow it to run the complete installation routine in order for it to complete.
    Just thought I'd post my experience in case it saves others some time and frustration.

    stilltrying wrote:
    Two weeks ago I did an install of Leopard to my Powermac G5. I upgraded from Panther. I have a 6 month old *Xerox Phaser 3100 MFP printer* hooked up to my mac via USB cable. Before I installed Leopard I could print PDFs with no problem.
    Hi guys,
    I also have a *Xerox Phaser 3100 MFP*: the device print well, but *the scanner don't work* with original xerox driver from xerom official support site.
    And you, do you have been scanner option with Leopard?
    And if yes, how?
    Thanks,
    mauro earthquake-man from L'Aquila (the G8-9-10.....-27 city!!)

  • Where is Support for Windows Update issues for Windows Server?

    Where is Support for Windows Update Issues for Windows Server?
    Windows Update keeps prompting to install an important update, KB2871690 and continually fails with error code 0x800f922
    I ran all the fixes I can find, it still fails.
    I also tried the manual install, fails.
    Microsoft used to provide no charge support for Windows Update issues. They additionally offer online fixes  for other versions of windows, but not server, and I can't find a forum.
    I also cannot ignore the update, it continually prompts.
    I ran the windowsupdate.diagcab and it continually states it fixes Windows Update error 0x80070057, by resetting windows update data store. It further states it fixes Problems installing recent updates.
    But it doesn't. I've run it 50 times, and it says the same thing every time.
    So there is no support for windows update, and no support for windowsupdate.diagcab.
    What's the deal?

    I've done the SFC/ SCANNOW and DISM
    here is the cbs.log
    What are we looking for?
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~BT\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360'. -
    CDISMManager::put_ScratchDir
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$Windows.~BT\sources" - CDISMManager::LoadLocalImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Dism.exe version: 6.2.9200.16384
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Executing command line: X:\$Windows.~BT\sources\dism.exe  /logpath:X:\$Windows.~BT\sources\Panther\cbs.log
    /scratchdir:X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360 /image:X:\ /is-serviceable
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\FolderProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\FolderProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\WimProvider.dll -
    CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\VHDProvider.dll -
    CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\VHDProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\ImagingProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\ImagingProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\CompatProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\CompatProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2013-12-04 19:48:20, Warning               DISM   DISM.EXE: Failed to load WimManager. Try running from the Deployment Tools Command Prompt. If the issue persists, ensure that wimgapi.dll
    and wimserv.exe are up to date.
    2013-12-04 19:48:20, Warning               DISM   DISM.EXE: Failed to add any commands.
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 physical location path: X:\ - CDISMManager::CreateImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Copying DISM from "X:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD"
    - CDISMManager::LoadRemoteImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Image Session: PID=1644 TID=1656 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Defaulting SystemPath to X:\ - CDISMOSServiceManager::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Defaulting Windows folder to X:\Windows - CDISMOSServiceManager::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Manager: PID=1612 TID=1616 Image session successfully loaded from the temporary location: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD
    - CDISMManager::CreateImageSession
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Setting SystemPath to X:\ - CDISMOSServiceManager::SetSystemPath
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Target image information: OS Version=6.2.9200.16384, Image architecture=amd64
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting the collection of providers from an image provider store type. -
    CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Get the registry path to the SOFTWARE hive located at X:\Windows\system32\config\SOFTWARE
    and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive
    2013-12-04 19:48:22, Info                  DISM   DISM Driver Manager: PID=1644 TID=1656 Further logs for driver related operations can be found in the target operating
    system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Current image session is [OFFLINE] - CTransmogManager::GetMode
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Determined WinDir path = [X:\Windows] - CTransmogManager::GetWinDirPath
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Product Type: [ServerNT] - CTransmogManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Processing the top level command token(is-serviceable). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the PE Provider.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Finalizing CBS core. - CDISMPackageManager::Finalize
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM OS Provider: PID=1644 TID=1672 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

  • Download for Samsung Printer Drivers v2.2

    Since the Samsung Printer Drivers v2.3 update i can not use my Samsung scanner (Samsung SCX-4500).
    What is the download link for Samsung Printer Drivers v2.2?
    Thanks.

    Hi guys, I have the same problem.
    The downloading scanner driver from the Samsung support center did not fix it, and the problem is caused from Samsung Printer Drivers v2.3 update befor scanner work well.
    I view that when show the Image Capture as The_Ben told the system consol show this error:
    PrinterProxy[901]: *** -[__NSArrayM objectAtIndex:]: index 0 beyond bounds for empty array
    PrinterProxy[901]: (
                        0   CoreFoundation                      0x0000000101a26fc6 __exceptionPreprocess + 198
                        1   libobjc.A.dylib                     0x0000000101897d5e objc_exception_throw + 43
                        2   CoreFoundation                      0x00000001019b4582 -[__NSArrayM objectAtIndex:] + 274
                        3   ImageCaptureCore                    0x00000001035e1135 -[ICScannerDevice handleScanParameters:] + 2839
                        4   Foundation                          0x0000000101cb41aa __NSFireDelayedPerform + 392
                        5   CoreFoundation                      0x00000001019dbc24 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
                        6   CoreFoundation                      0x00000001019db776 __CFRunLoopDoTimer + 534
                        7   CoreFoundation                      0x00000001019bc001 __CFRunLoopRun + 1617
                        8   CoreFoundation                      0x00000001019bb676 CFRunLoopRunSpecific + 230
                        9   HIToolbox                           0x0000000107ead31f RunCurrentEventLoopInMode + 277
                        10  HIToolbox                           0x0000000107eb45c9 ReceiveNextEventCommon + 355
                        11  HIToolbox                           0x0000000107eb4456 BlockUntilNextEventMatchingListInMode + 62
                        12  AppKit                              0x00000001021b0f5d _DPSNextEvent + 659
                        13  AppKit                              0x00000001021b0861 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
                        14  AppKit                              0x00000001021ad19d -[NSApplication run] + 470
                        15  AppKit                              0x000000010242bb88 NSApplicationMain + 867
                        16  PrinterProxy                        0x00000001017d9b48 PrinterProxy + 6984
                        17  ???                                 0x0000000000000002 0x0 + 2
    any ideas?

  • Hi, I couldn't download apps on my iPad 1. It say iOS update required for this action whereby my software is the latest 5.1.1

    I couldn't download apps using my iPad 1. It says that iOS update required for this action.

    Some developers allow you to download older compatible versions of their apps. If it's a free app then try downloading the current version on your computer's iTunes so that the app is in your purchase history, then on your iPad go to the Purchased tab in the App Store app and see if you can download an older compatible version of it. If it's a paid-for app then contact the developer first and ask them if the above will work, don't buy it and then find it won't

  • Need proper device type for Xerox printer "WorkCentre 5755. 5775, 5790"

    Hi ,
    Could anybodies suggest the proper device type for *"Xerox printer "WorkCentre 5755. 5775, 5790".
    Thanks
    Regards
    Priyabrata Mishra

    Hi Sujit,
    I need he information about the device types for these printer models
    Work Centre 5755/5775/5790
    Please suggest if there is any compatible device types available in the given link by you. I have already downloded all the device types from this link but there is no device type information for these mentioned printer models above. Please suggest
    Thank you so much for giving your valuable time
    Regards
    Priyabrata

  • Hardware requirements for sap bw3.5 in windows environment

    Pls help me the hardware setup(harddisk,ram etc) required for SAP BW3.5 in windows environment.
    thanks in advance..
    Regards
    Ganesh

    Hi,
    HDD : 100GB
    RAM : 1 GB
    regards,
    Raju

  • Printing from Windows 8 to a shared printer on a Windows 7 machine

    WE have a a user that has a laser printer on A windows 7 machine that others in the office can access EXCEPT the one person on a Windows 8 machine. We have tried everything, but cannot get her to print to this printer. Says it cannot be found. What does
    Windows 8 need to see a printer on a Win 7 workstation. She does have access to network printers and her own.
    Thanks.

    We have the same kind of problem but a bit different.
    Dell Printer (used for years shared on a network) was moved to our Windows 7 machine plugged in via USB.  We only use a plain workgroup with no Domain as we also have Macs on the network.
    I have Macs using shared printer, a Windows XP using the shared printer, and even Windows 7 under Parallels on the Macs using the shared printer no problem.
    I had the lone Windows 8 laptop using the shared printer but then it just stopped working.  So I deleted it and now when I try to add it is want credentials and none work.  It will not connect to the shared printer on the Windows 7 machine.
    I have Windows 7 (which also has a couple shared drives that do work) set for No Homegroup and No Password for sharing - pretty much open as we are behind a Cisco Firewall to the outside.  No firewalls on the pcs.
    Not sure where to go from here...

  • Can we run domain controller windows 2008 32 bit and additional domain controller on 2003 server

    im my environment we are trying to upgrade from server 2k3 to 2k8, out testing done on server 2k3 to 2k8, but can we run domain controller windows 2008 32 bit and additional domain controller on 2003 server ...kindly suggest
    Nitin Gaurav
    [email protected]

    Yes you can. If you have two 2003 AD servers currently and upgrade one of them to 2008 AD then they'll continue to be able to work together. The domains functional level will remain as 2003 across both servers so at this stage you won't get any benefit from
    the new AD functionality available in 2008.
    Once you've then upgraded the second 2003 server to 2008 you can then upgrade the functionality levels in AD to make it 2008. It's been a while, but I believe it doesn't happen automatically, so once all AD servers have been upgraded you have to go into
    AD and upgrade the functionality levels yourself.

  • Deleting print drivers on Windows Server 2008 R2 without Print Role

    Hi,
    I'm using Windows Server 2008 R2 with Citrix Xenapp for published desktops meaning that i need to add a number of different printers to the server for the various users. Unfortunately i have some printer drivers that i think are conflicting and want to remove
    these from the server.
    How can i do this without adding the Print and Document Services role? Without this role i don't believe i can access 'Print Management' in the same way that i would with a Windows 7 client and then remove the driver package.
    Is there another way that i can do this or should i be adding this role just to remove these drivers and then perhaps removing the role (if necessary), assuming that this is possible?
    Thanks for any help.

    add the tools for print management
    in elevated cmd window
    dism /online /enable-feature /featurename:Printing-AdminTools-Collection
    If you already have local shared prints on the server, add the role.  Adding the Role installs the tools and opens the File and print sharing firewall port which would have been achieved by adding a shared printer. You do not need to add the Print
    role to setup a machine as a print server, it's not a requirement. 
    Alan Morris Windows Printing Team

  • Cannot install OS X 10.6.2 Update or Hewlett-Packard Printer Drivers

    Error message #1: "Mac OS X Update can't be installed on this disk. This volume does not meet the requirements for this update."
    Error message #2 (regarding Printer Drivers): This volume does not meet the requirements for this update.
    Disk in question is the startup volume. It has 164.35 GB free. OS X 10.6 was just installed about two hours ago, and the two updates were downloaded right after 10.6 was installed.

    Is the drive partitioned using GUID and formatted Mac OS Extended, Journaled? Have you done this:
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    Are you installing the 10.6.2 Combo Updater (not the incremental one?) The latter is slightly larger and has the word "Combo" in the title.
    Did you update to Snow or did you install it on a freshly erased hard drive?

  • Windows 7 x64 can't read/install any printer drivers from Windows Server 2003 x64 (AMD64 folder and HP Deskjet 855c)

    I read the thread Widows 7 printer
    HP deskjet 855c driver about possible installation of HP855c drivers onto Windows 7 x64 from "Windows Server 2003 x64" CD but I didn't have enough luck to succeed with doing it on my laptop. That thread appears to be dead now
    as it is marked "Answered", so I'm asking for help here. I have Toshiba Satellite P500 with Windows 7 Home Premium 64-bit (http://i55.tinypic.com/2zgth6v.jpg). 
    Let me tell you first that I don't have access to Windows Server 2003 x64 or XP Pro 64 CD's. However I did some research online, which eventually forced me to learn about the "file sharing". After extensive search I was able to get the copies
    of AMD64 folders from Windows Server 2003 R2 Standard x64 with SP2 and
    XP Pro 64. The reason that I went also after XP Pro was because I thought that the extra wording "R2 Standard x64 with SP2" in description of "Windows Server 2003" did not reflect the exact name provided by poster
    Alan. I couldn't find just "Windows Server 2003 x64" (does it matter?).
    Anyway, I followed first the drill with running "printui /s /t2" and disabling UAC, and then in both cases I was able to locate the
    NTPRINT.INF file (http://oi51.tinypic.com/9qwvt2.jpg - this image is from XP Pro AMD64 folder) but each time when I
    attempted to install the driver, I got the same message stating:
    "The folder you specified doesn't contain a compatible software drive for your device. If the folder contains the driver, make sure it's designed to work with Windows for x64-based systems." (http://oi53.tinypic.com/27yveiw.jpg)
    Why aren't there x64 drivers?
    During several installation attempts I had the printer connected to or disconnected from my laptop. It didn't make any difference. I must add that for this purpose I had to use different cable than the original one designated only for the
    Parallel port in my old desktop with Windows XP. My new laptop with Windows 7 x64 came only with 3 USB ports (plus 1 HDMI and 1 Serial). Because of that situation I bought in advance a new printer cable called “USB to 36-pin Parallel Port Adapter
    Cable” (http://www.amazon.com/gp/product/B003A8I75E). I'm not sure, if it will work until I can install the printer.
    Besides, nobody talked about this issue yet. I was also playing with the port choices in "Add printer" step; changing from default LPT1 to USB001 with the same negative results.
    I don't know what I'm doing wrong. I was very hopeful after reading positive "case closed" notes there.
    Can anyone help me here, maybe by making the necessary files available for download? I'm willing to pay for such assistance or make a donation, if necessary. Seriously. Judging by the large number of views of the original
    thread, one could assume that there is a potential demand for such service. It would be more human to pay few bucks for a few driver files than $900 for the whole Windows Server 2003 x64 CD, no? Can Microsoft accomodate me/us, please? :)
    Andrew*
    P.S. I was advised to come for help here from
    http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/windows-7-x64-cant-readinstall-any-printer-drivers/4e7d06e1-33a5-4597-be70-4fdc087a63a7?msgId=9a045994-0d31-4d40-b17d-dba372393ee4

    I have my HP 855c/driver working on Win 7 Ultimate x64. I used the 'printui /s' procedure and 4 files described above with some minor changes.
    I pulled WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe down from the Microsoft website. Running the file causes the exe to unpack into a temp folder at the root drive. A 'Setup Error' message box is displayed once the file is run. I left this
    message box up until I copied ntprint.inf, ntprint.cat, and sp2.cab from the temp folder.
    I copied driver.cab from a Windows XP Pro disc. I also needed amd64\stdnames.gpd which was already in my Windows 7 c:\windows\system32\spool\drivers\x64\3 folder.  
    I created a folder with the 5 files (ntprint.inf, ntprint.cat, sp2.cab, driver.cab, and amd64\stdnames.gpd). This is my 'Have Disc' folder. 
    I followed the 'printui /s' instructions, first changing the permissions mentioned above and then installing the driver. Next I followed the instructions to add a printer from Control Panel 'Devices and Printers' - 'Add Printer', choosing to 'use an existing
    driver' when installing the HP 855c.
    I used a slightly different ntprint.inf, size 1570418. The readable contents of ntprint.inf is as follows. Notice the line 'CatalogFile=ntprint.cat' is not included. I tried using the 1570468 version of ntprint.inf; when I did I received an incompatibility
    message (probably the same one mentioned above).
    ; NTPRINT.INF (for Windows Server 2003 family)
    ; List of supported printers, manufacturers
    [Version]
    Signature="$Windows NT$"
    Provider=%MS%
    ; LayoutFile=layout.inf
    ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
    Class=Printer
    DriverVer=10/01/2002,5.2.3790.4533
    [ClassInstall32.NT]
    AddReg=printer_class_addreg
    [printer_class_addreg]
    HKR,,,,%PrinterClassName%
    HKR,,Icon,,"-4"
    HKR,,Installer32,,"ntprint.dll,ClassInstall32"
    HKR,,NoDisplayClass,,1
    HKR,,EnumPropPages32,,"printui.dll,PrinterPropPageProvider"
     Good luck

Maybe you are looking for

  • WEB SERVICE PROXY GENERATED USING 11.1.1.5.0 WSDL FAILS WITH 11.1.1.6.0

    I have created a Web Service Proxy project in Jdev using BI Publisher 11.1.1.5.0 WSDL (ReportService). Generated ReportService_Service method uses following QName to get the port: namespaceURI = "http://xmlns.oracle.com/oxp/service/v2" localPart = "*

  • RoboHelp Packager for Adobe AIR (BETA)

    It is so exciting. It been just a few months since we released Adobe RoboHelp 7 and a brand new Technical Communication Suite, and today we are ready to share with you guys what we perceive as the future of Online Help. All I can say is that Time fli

  • How can I use my addons once they're installed? Where do I go? Is there a Firefox toolbar?

    I'm on a Mac. I installed MeasureIt and RankChecker as addons. I need to install a couple more. How do I use an addon once I have it? Do they show up in a toolbar somewhere? I don't see them in the Google toolbar for Firefox, or above the Google tool

  • How can I embed a photo into macmail?

    I don't want to send it as an attachment but would like for it to show up in the body of the e-mail. What should the format be? I've tried cutting and pasting but that ends up as an attachment. Thanks!

  • Printing size problem in Lightroom 5

    I need help. When I print from Lightroom 5 with the settings noted in these screen shots I do not get the proper size print. You can see that I'm using 17" X 22" paper and the print should be 14.003" X 21.042" which is a 1.5 aspect ratio. From the fi