U2414H DP 1.2 STD questions

Similar Questions

• U2414H DisplayPort 1.2 STD Set Up - monitors will not get video Signal from the graphics card during start or restart

  * What specific Dell monitor? 2 two U2414h monitors with MD214 - package of multi-monitor support
  * What specific model of computer, desktop/laptop? Workstation HP xw8400, Intel Quad Core Xeon CPU E 5335 @ 2.00 GHz, 4.00 GB of memory
  * What operating system? Windows 7 Professional 32-bit
  * Which video card? AMD over-pants V3900
  * Which ports are available for the video card? DisplayPort 1.2 STD, Dual-link DVI
  * Which video output from the video card port video on the port monitor do you use? Output Mini DisplayPort Display port in
  * What cable are you using to set the video card to the monitor? Adapter DisplayPort to MiniDispayPort - we came with every Dell monitor
  * You use the Dell supplied cable? Yes - two monitors

  * Press the Menu button of the monitor to open the OSD (On Screen Display). The bottom of the screen should display a resolution. This resolution should match the resolution of the default monitor. The two monitors: 1920 x 1080, 60 Hz

  * Brief description of the problem monitor? Monitors have been implemented following the instructions on page 25 of the Dell online manual to connect the monitor to function DP multi-flow (MST). DisplayPort cable is connected to V3900 output MiniDisplay port DisplayPort graphics card in the 1st U2414H; second DisplayPort cable is connected to the DisplayPort on 1 U2414H monitor output and MiniDisplayPort in the 2nd monitor U2414H. Dell U2414H drivers have been installed from the CD provided and both recognized by Windows. V3900 graphics card Driver is up to date with the EyeInfinity software. Source of input on both monitors the Mini Display Port value. Display settings on both monitors Display Port 1.2 value activate. Resolution of the screen on Windows 7 shows: (a) two separate Dell U2414H (mini Display Port) screens, with each resolution 1920 x 1080, multi (b) displays the value "to extend these displays. The two views work with Setup leading up to and acknowledged by the graphics card.

  Problem 1 - all the time - monitor power buttons are lit, the computer is turned on, then monitors lights don't - they show 'Power save mode' and then turns off. To hit the power button on the computer to shut down Windows. Only way to get these on monitors is unplug cords from the back of each monitor, wait a few minutes, plug in the power cord, start computer and then both monitors will start up and sign of windows to the screen will appear and monitors will work. Normal operations for a full day of work if you do not restart. If you need to restart during the day (like when you get a software update), the same thing happens. Start the computer to restart, but the monitors come back on not and remain dark. There is nothing wrong with the graphics card V3900. He is certified by AMD and DisplayPort.org to work in an environment of STD DisplayPort 1.2. I had previously two 215tws Samsung SyncMasters connected to each output V3900 Grahics card and they work very well in extended mode for years until a SyncMaster 215tw started shaking like crazy. A SyncMaster has been connected to the out display with a dongle and a DVI cable Port. The other SyncMaster was connected to the DVI output on the graphics card. So I decided to buy these two U2414Hs. Technical support Dell after many phone calls and e-mails finally advised me that there is a problem of "compatibility" between my computer and the U2414Hs and recommended that I return the monitors. On the web site of the U2414H AMD has not been certified by AMD to work in a DisplayPort 1.2 STD Set Up. Other former Dell monitors are certified by AMD to work in the Display Port 1.2 Setup. DisplayPort.org lists the U2414H to work with Display Port (it does not say that it will work in a DisplayPort 1.2 Set Up).

  Problem 2 - shift perceptible in the entrance of Microsoft Blue Tooth keyboard and mouse and PS2 Keyboard and mouse. All the drivers are up to date. When you type a phrase, it takes a few moments for the text displayed on the screen using a keyboard. Both the mouse connected and the Bluetooth mouse are unresponsive sporadically for a few moments until they finally react. It happens regularly during the day. The monitors provide excellent clarity when you work. The stand is ideal for office property. Before these monitors are returned if no one knows what causes these two problems and does anyone have a solution? Should I stop using the Display Port 1.2 and hang them using HDMI with active dongles? If I have to return these two U2414Hs, I considered the 2 two U2413s. Someone at - it all opinions on the last U2413s from Dell? I have read some real problems with ghosting that I just haven't the time for more. The remanence correction in the models of U2413 sold in 2014? There are very few monitors on the market with Display Port in and out to the back to support DisplayPort 1.2 STD Transport.

  Thanks for any input.

  I had to remove my VGA HDMI DV card and now the DP (display port) works very well. Don't need to use a HDMI cable. Display Port 1.1 is reported as the problem in order to remove the card solves this problem.

• Resolution of U2414H DisplayPort Daisy Chain/STD problem

  Hello

  I have what seems to be a common problem with no solution on these pages; with DisplayPort STD.

  I had two of these Dell monitors over the weekend and spent about 3 hours trying to get STD to work with them. I arrived later, and they have worked fine for about 36 hours.

  In this time my computer restarted two times without any problem. However, this morning I had upward, turned and suddenly the second (end of my STD string) string is not recognized as an instructor. It shows my desktop, but only at 640 x 480. AMD Catalyst can see it, but refers to it as 'No Display connected.

  My setup is a Gigabyte Radeon HD 7950 feeding these two Dells (on a single string of DP STD), a Compaq Q2022a on HDMI and a DVI. The first dell also has a USB Bluetooth stick and WiFi USB dongles plugged, and the second dell USB tire this is the capacity of the first. Both worked absolutely fine when I went to bed, and this morning, the second in the chain was not.

  I am looking to buy up to four more of them for a tri-moniteur stacked configuration, but I need them to be more reliable before I can justify spending that much! I love the thin bezel and STD is a must for the configuration I want, but reliability is essential too, I don't want to spend an hour a day fixing everything...

  Thank you

  For anyone interested, my workaround is the following:

  -Unplug the monitor two monitor one

  -Disable STD on monitor 1

  -STD re - activate the monitor 1

  -Reconnect the monitor 2 in 1

  -Hold the power for about 8 seconds on Monitor 2

  Seems to work after having done this, not.
  Of course, a better solution would be for Dell to realize they sold a product of poor quality, do a recall and get fixed them correctly. This is currently my only product of Dell and if this is how their quality control, I certainly won't be getting more.

• Windows 2008 Server R2 Std - issue of Best Practice Analyzer

  Windows 2008 Server R2 Std - question BPA
  I built a new Windows 2008 R2 Standard Server and configured as a domain controller. When you run the BPA I get the following error, which I can not solve:

  Question:
  The default domain controllers policy is not in force on the OR OR = Domain Controllers, DC = WRIGHT.
  Impact:
  If the Group Policy settings that are defined in the default domain controllers policy are not applied to domain controllers, Active Directory operations may fail.
  Resolution:
  Link the default domain controllers policy to the ORGANIZATION OR unit = Domain Controllers, DC = WRIGHT

  The default domain controllers policy is linked to the domain controllers OU. I dun dcdiag and the only failure is NCSecDesc but I don't plan to add an RODC to the forest. When I run the resulting strategy game I can see domain controller policy has been applied.
  Is there something I can do to clear this error message?

  Hello Lynn Furlong,

  Microsoft Communities is for consumer issues on Windows 8, Windows 7, Windows Vista and Windows XP. Your question deals with Windows 2008 Server R2, it would be better to post your question in the forums TechNet for ITPros.
  Click on the link here to transfer your question in the Forum Windows Server 2008 Group Policy. They will be better able to meet your group policy do not apply to domain controllers.

  Sincerely,

  Marilyn

• U2414H, Dual, laptop, Windows 10, Nvidia GTX 960 M, no STDS to the second monitor?

  Hi all

  I hope that I have included all relevant information in the present, but ask if I missed something. I bought two of the screens U2414H and a Windows 10 laptop computer powered by GTX 960 M with HDMI and Mini DP ports. My goal was to be able to the Garland of the whole U2414H screens so I could use my laptop out and about, and when connection back to the monitors of would have to plug in a cable and get two screens. In theory, but...

  I followed the instructions and using two Mini-DP to DP cables, connected the mini laptop RFP RFP on the first screen. DP on this same screen highlights Mini DP on the second monitor. I activated the DisplayPort 1.2 on both of these screens. I can't get any signal on the second monitor, it boils down to the power saving mode.

  Otherwise, I decided I would try using two cables and ditch the idea of DP STD I can at least use the two screens. So I have laptop HDMI to a screen and the MiniDP to another, and therefore, that alone will never work at a time. Individually, they work very well, both with HDMI or DP. But the two connection fails every time. When I tried to connect a display of alternative supporting HDMI as the second, which works very well.

  So I had an autour reading and it seems that it is common to have problems of connectivity to these screens. This brings me well on my two questions:

  (1) is there something that would work?

  (2) assuming that there is nothing that works, Dell can swap these screens for two that will achieve what I need?

  Thank you

  Dave

  In MST, DP 1.2 should be turned off (disabled) on the second monitor.

  Laptop AMD on--> U2414H CDM to cable DP--> DP U2414H #1 in (DP 1.2 enabled) (Port #3 in the image)

  
  #1 U2414H (Port #5 in photo) DP--> DP U2414H CDM cable--> 2 # U2414H CDM in (DP 1.2 disabled) (Port #4 in photo)

  When you use only no STDS, is the lid of the laptop open all trying to run two monitors of U2414H? This laptop can even run three screens, laptop LCD + 1 # U2414H + 2 # U2414H?

• U2414H questions

  I bought a u2414h about a month ago and he has this really weird problem. In the center of the screen it looks like there is semi transparent vertical lines. It's hard to describe, but it looks like the lower part of this picture.

  

  Some things ive noticed in trying to figure out the cause:
  -the lines don't change or move when moving an image on the screen.
  -filter ag is supposed to be cross free hatching and seems to be consistent when the screen is off
  -ive tried different cables and it does make a difference.
  -ive hooked the monitor up to your laptop to make sure it's not not my video card and the lines were always there.
  -l' effect comes and goes. sometimes its almost the size of the Palm of your hand and very sensitive for a few days its barely there.

  any ideas of what could be the cause?

  Run monitor factory reset, self-test, SUBMISSION (built-in diagnosis) by these instructions that remove troubleshooting computer and wiring. You see the problem when you run the tests? If so, get it exchanged if still within the warranty period of 3 years. If you don't see the question, the culprit is the graphics card, graphics card Driver or the wiring.
  -If the replacement screen does not have the problem, return the original monitor to Dell using the return packing slip.
  -If the replacement screen has the same question, the monitors were not the culprit in the first place. Send the replacement back and keep the original. Turn to the system, the video card or card video as the culprit driver.

• Question 2: BD / BD more STD (cs4)

  Just started work with Blu - Ray through the creation.  Wow, what quality!  Two questions, if someone wouldn't mind help out me.

  (1): I ran into the problem with the audio length needing to be reduced in size is less than the length of a video on the time line in again.  Is this something that is widely known and likely to be dealt with in CS5?

  (2): can a disc include BD sequences both Std - each being read in specific properties out there on the final drive?  Or does only use BD HD on Blu - Ray and regular DVD STD sequences?

  Would appreciate any ideas.

  Thank you

  Patrick

  1. Please explain.

  2 No, Yes.

• U2414H - question Daisy chaining

  Trying to get U2414H monitor purchased from Dell daisy chain with MS Surface Pro 3 (8.1) (all updates made). Driver for the monitor is also downloaded and installed.

  Have Surface Pro 3 dock miniDP to DP (en) U2414H then (out) DP / DVI on 3rd screen.

  I activated PD 1.2 on the Dell and I can extend screens of the Surface of the U2414H very well.

  I clicked on "detection" to see if it detects the screen which is attached via DP to DVI cable and it gives ONLY the option to connect via VGA.

  I could go buy a DP to VGA cable and hope that it would work with that, but why the options do not have a choice of DVI? If possible, please let me know what to do to get this choice.

  Thank you

  Katrina

  Update: ordered another monitor U2414H, but none of the cables provided with this worked. I had to order a cable of DP to DP to connect two monitors. DPout used in the RPI and it works fine now.

• Power U2414H / Initialize question

  Last week, I bought three monitors Dell U2414H.

  One of them seems to keep restarting.
  NOTE: Only the power connector is connected, so no USB, no HDMI and no DP cable is connected.

  When I turn on the screen sometimes some vertical green lines appear in the contrary case the Blackwatch screen or watch a few dark vertical lines.
  After a few seconds (random), the monitor turns and turns immediately again.

  Sometimes I'll see the backlight just before the monitor goes blank again.

  It is not possible to open the OSD menu and it is not even possible to turn off the monitor (without disconnect).

  NEW: The problem seems even with only a plugged power cable, so I don't really know what is not a problem of software/driver/GPU. It seems to be a hardware/firmware failure.

  When I also connect the USB port, Windows reads the sound "connected equipment" and "disconnected material" and maintains this repetition based on the monitor switch on/off.

  Is this a known problem or can it be fixed?

  mastermattie,

  Not a problem known and not, can not be solved. This monitor should be exchanged. You buy them directly from Dell?

• Dell U2414h menu gone? Keys no longer work?

  My Dell U2414h monitor is connected to the end 2012(El Capitan) Apple Mac Mini HDMI. After 1:30, I can't go back in the Menu of the Dell printer. It seems as if the touch buttons no longer work. It seems that if the menu is somehow locked.

  The only thing dat will work is cut off from the power supply. After that work very good tactile buttons, but after a while or when I closed the Mac Mini, I can't go back in the menu. The Dell monitor is now also waiting because I cannot 'touch' the power button.

  Someone know what I did wrong or is something wrong with the Dell U2414h or is it something in the Apple Mac Mini?

  I asked the same question in the Forum and they said that it might have something to do with my Apple Mac Mini.

  During the Forum, they gave me a solution that does not work for me:

  Reset the U2414H and re - test
  * Turn on the computer and monitor off
  * Disconnect all cables from the screen, including the power cable
  * Press the power monitor in 30 seconds button
  * Plug the monitor cables for the monitor and the video card of the computer. There should be only one cable video connection from the monitor to the video card
  * Turn on the monitor, then the computer

  Note, as this model was not tested/validated on the proprietary Apple hardware, ports, and the software, you must also post on the Apple Forum of Discussions and see if they can offer an overview or troubleshooting steps.

  
  

  Also does not work the solution in the manual to touch the power button for 10 seconds.

  
  

  Someone knows what's the problem?

  I think it is likely yo have a problem with the monitor. The video and does not interact with the onscreen menu/controls.

  -Try to reset memory NVRAM/PRAM and SMC

  MacIntel: Reset of the controller (SMC) system management

  Subject of memory NVRAM and PRAM

• Update SP2 from 2003 to 2008 Std - update, due to lack of InstallWindows:Error Type = 3211266

  Hello

  Really struggling with an upgrade from 2003 SP2 Std 2008, it's a PC that is inherited. Installation goes completely to 100% then says failed and will return in 2003 again.

  Logfile below. -anyone any ideas please? and thanks for looking.

  2016-04-14 18:43:56, error [0x08081e] MIG could not load manifest to C:\$WINDOWS.~BT\Sources\dlmanifests\errorreportingfaults-dl.man: class UnBCL::XmlException: hResult = 0 x 0 = 2 line, Position = 134; .
  void __thiscall UnBCL::XmlDocument:Load(class_UnBCL::String_*)

  2016-04-14 18:48:31, [0x08071d] MIG CDownlevelOCStore::GetOCCollection error, failed to load C:\$WINDOWS.~BT\Sources\dlmanifests\errorreportingfaults-dl.man. : Class UnBCL::XmlException: hResult = 0 x 0 = 2 line, Position = 134; .
  void __thiscall UnBCL::XmlDocument:Load(class_UnBCL::String_*)

  2016-04-14 18:48:43, error [0x08081e] MIG could not load manifest to C:\$WINDOWS.~BT\Sources\dlmanifests\errorreportingfaults-dl.man: class UnBCL::XmlException: hResult = 0 x 0 = 2 line, Position = 134; .
  void __thiscall UnBCL::XmlDocument:Load(class_UnBCL::String_*)

  2016-04-14 19:07:49, error [0x06015d] IBS EnumVdsDisksCallback: found the disk with an invalid name. [gle = 0x000036b7]
  2016-04-14 19:08:01, error [0x06015d] IBS EnumVdsDisksCallback: found the disk with an invalid name. [gle = 0x000036b7]
  2016-04-14 19:22:53, error [0 x 080792] MIG COCEventTracing::COCEventTracing call failed StartTrace 87. [gle = 0 x 00000057]
  2016-04-14 19:27:28, error [0x0802b6] MIG could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [EventMessageFile]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [EventMessageFile]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 19:27:28, error [0x0802b6] MIG could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [TypesSupported]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\AutoEnrollment [TypesSupported]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 19:27:28, error [0x0802b6] MIG could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\Tlntsvr [EventMessageFile]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\Tlntsvr [EventMessageFile]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 19:27:29, error [0x0802b6] MIG could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [EventMessageFile]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [EventMessageFile]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 19:27:29, error [0x0802b6] MIG could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [TypesSupported]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\DfsSvc [TypesSupported]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 19:27:29, error [0x0802b6] MIG could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [EventMessageFile]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [EventMessageFile]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 19:27:29, error [0x0802b6] MIG could not create object: HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [TypesSupported]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\SCardSvr [TypesSupported]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:13:49, error [0x0802b6] MIG could not create object: HKLM\SOFTWARE\Classes\EventPublisher.EventPublisher\CurVer. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the [HKLM\SOFTWARE\Classes\EventPublisher.EventPublisher\CurVer] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:13:49, error [0x0802b6] MIG could not create object: [HKLM\SOFTWARE\Classes\EventPublisher.EventPublisher\CurVer]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\SOFTWARE\Classes\EventPublisher.EventPublisher\CurVer []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:15:26, error [0x0802b6] MIG could not create object: [HKLM\SOFTWARE\Classes\InternetShortcut\shell]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\SOFTWARE\Classes\InternetShortcut\shell []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:15:26, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\InternetShortcut\shell\print\command]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\InternetShortcut\shell\print\command []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:26, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\InternetShortcut\shell\printto\command]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\InternetShortcut\shell\printto\command []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:26, error [0x0802b6] MIG could not create object: [] HKLM\SOFTWARE\Classes\InternetShortcut\shellex\ContextMenuHandlers\ {FBF23B40-E3F0-101B-8488-00AA003E56F8}. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\SOFTWARE\Classes\InternetShortcut\shellex\ContextMenuHandlers\ {FBF23B40-E3F0-101B-8488-00AA003E56F8} []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:15:26, error [0x0802b6] MIG could not create object: [] HKLM\SOFTWARE\Classes\InternetShortcut\shellex\PropertySheetHandlers\ {FBF23B40-E3F0-101B-8488-00AA003E56F8}. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\SOFTWARE\Classes\InternetShortcut\shellex\PropertySheetHandlers\ {FBF23B40-E3F0-101B-8488-00AA003E56F8} []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.application\DefaultIcon]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.application\DefaultIcon []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.application\shell\open\command]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.application\shell\open\command []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xaml\DefaultIcon]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xaml\DefaultIcon []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xaml\shell\open\command]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xaml\shell\open\command []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xbap\DefaultIcon]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xbap\DefaultIcon []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xbap\shell\open\command]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xbap\shell\open\command []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xps\DefaultIcon]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xps\DefaultIcon []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:43, error [0x0802b2] MIG could replace not subject: [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xps\shell\open\command]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\SOFTWARE\Classes\SystemFileAssociations\.xps\shell\open\command []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:15:54, error [0x0802b6] MIG could not create object: [HKLM\SOFTWARE\Classes\XML\OLEScript]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\SOFTWARE\Classes\XML\OLEScript []], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b2] MIG could not replace object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [comdlg32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [comdlg32]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:19:41, error [0x0802b2] MIG could not replace object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [imagehlp]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [imagehlp]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [lz32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [lz32]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b2] MIG could not replace object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [oleaut32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [oleaut32]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [olecli32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [olecli32]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [olecnv32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [olecnv32]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [olesvr32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [olesvr32]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b2] MIG could not replace object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [shell32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [shell32]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [url]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [url]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b2] MIG could not replace object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [urlmon]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [urlmon]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [version]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [version]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b2] MIG could not replace object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wininet]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wininet]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:19:41, error [0x0802b2] MIG could not replace object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wldap32]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip, delete the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wldap32]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Delete(struct_Mig::IMigLocation_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wow64]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wow64]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wow64cpu]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening the registry entry [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wow64cpu]], which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:19:41, error [0x0802b6] MIG could not create object: HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wow64win]. Mig::Win32ErrorException exception class: Win32ErrorException: Error (0), Skip opening [HKLM\System\CurrentControlSet\Control\Session Manager\KnownDLLs [wow64win]] registry entry, which is protected by WRP...
  void __thiscall Mig::CRegistryDataStore:Create(class_Mig::CDataUnit_*)

  2016-04-14 20:22:01, error [0x08030a] MIG MigDoMigration caught exception: class UnBCL::ArgumentOutOfRangeException: startIndex and rank value.
  __thiscall UnBCL::String:String(const_unsigned_short_*,int,int)
  [gle = 0x000003f0]

  ______________________________

  Other end of log file

  2016-04-14 20:22:16, info [0 x 080658] MIG nothing to clean. E:\$INPLACE.~TR\Machine does not exist
  2016-04-14 20:22:16, info [0 x 080658] MIG nothing to clean. F:\$INPLACE.~TR\Machine does not exist
  2016-04-14 20:22:16, info [0 x 080658] MIG nothing to clean. G:\$INPLACE.~TR\Machine does not exist
  2016-04-14 20:22:16, info [0 x 080658] MIG nothing to clean. H:\$INPLACE.~TR\Machine does not exist
  2016-04-14 20:22:16, info [0 x 080658] MIG nothing to clean. I:\$INPLACE.~TR\Machine does not exist
  2016-04-14 20:22:16, stop Info [0 x 080279] complete MIG of the file system manager in place.
  2016-04-14 20:22:16, mapping of information [0x0803e6] removal of MIG for HKLM
  2016-04-14 20:22:16, info [0x0803e7] MIG successfully unmapped HKLM
  2016-04-14 20:22:16, mapping Info [0x0803e6] removal of MIG for HKU
  2016-04-14 20:22:16, info [0x0803e7] MIG successfully unmapped HKU
  2016-04-14 20:22:16, the analysis service of information [0 x 080487] MIG destroying BONE
  2016-04-14 20:22:16, the analysis of information [0 x 080488] destroyed MIG OS service
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xc08].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0x3f0].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xdb4].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xe68].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xe5c].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xcdc].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xcd4].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xeec].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID = [0xef0] output.
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0 x 348].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xa40].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xbe4].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID = [0 x 220] output.
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0x90c].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID = [0 x 870] output.
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xdf4].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID = [0 x 924] output.
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0xbc4].
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID = [0x1ac] output.
  2016-04-14 20:22:16, MIG MigHost info: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: exit ThreadID = [0x92c].
  2016-04-14 20:22:16, COutOfProcPluginFactory::FreeSurrogateHost MIG Info: stopping.
  2016-04-14 20:22:16, MigHost MIG Info: process exit.
  2016-04-14 20:22:16, Info [0x0804ae] MIG CMigWorkingDirHelper: removal of C:\$UPGRADE.~OS\OnlineUpgradeApplyWork working directory
  2016-04-14 20:22:16, method of information leaving MigShutDown
  2016-04-14 20:22:16, info [0x08008d] MIG migrate: Finish (0)
  2016-04-14 20:22:16, WARNING [0x08076e] MIG UpgApply: (C:\$UPGRADE.~OS\OnlineUpgradeStore) restore did not complete successfully
  2016-04-14 20:22:16, info [0x08059e] MIG leaving Callback_ApplyNewSysMachineSpecific (failure)
  2016-04-14 20:22:16, PublishCriticalError MIG Info: Windows Setup has encountered an error and cannot continue.  Your computer will now reboot and your previous version of Windows is restored.
  2016-04-14 20:22:16, info [0x0a013d] UI accept Cancel. Leaving the Page's progress.
  2016-04-14 20:22:16, current user interface pages and destination Info [0x0a013e] are the same. Judgment of navigation.
  2016-04-14 20:45:12, CallBack_DiagnosticDataSend DIAG Info [0 x 070042]: called with the notification of error published by ErrorHandler
  2016-04-14 20:45:12, info [0x0a0023] run UI ProgressInfo\SendDiagnostics task: StartProgress
  2016-04-14 20:45:12, CallBack_DiagnosticDataSend DIAG Info: Phase = 4 start time was 0X30D2073BA, end time was 0X30D208448, total was 0X108E
  2016-04-14 20:45:12, CallBack_DiagnosticDataSend DIAG Info [0 x 070044]: startSetupTimeInSecs = 0X30D2072BA
  2016-04-14 20:45:12, info [0 x 070045] DIAG diagnosis treatment given to the 2016-04-14 20:45:12
  2016-04-14 20:45:12, CallBack_DiagnosticDataSend DIAG Info [0 x 070046]: endSetupTimeInSecs = 0X30D209258
  2016-04-14 20:45:12, DIAG CallBack_DiagnosticDataSend info: setupInstallTime = 0X1F9E
  2016-04-14 20:45:12, DIAG CallBack_DiagnosticDataSend info: the user is NOT ACCREDITED-IN M² and Watson.
  2016-04-14 20:45:12, info [0x0a0024] run UI ProgressInfo\SendDiagnostics task: EndProgress
  2016-04-14 20:45:12, info [0 x 090095] PANTHR called WdsExitImmediate!  The execution stops and the queue will not be saved.
  2016 04-14 20:45:12, info [0x09008c] PANTHR SeqExecute - stop, since WdsExitImmediate() has been called
  2016-04-14 20:45:12, info [0 x 090086] PANTHR pWorkerThreadFunc - stop
  2016-04-14 20:45:12, info [0 x 090086] PANTHR pWorkerThreadFunc - stop
  2016-04-14 20:45:12, info [0 x 090086] PANTHR pWorkerThreadFunc - stop
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: SkuAssembly (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: MigTestPlugin (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: ErrorHandler (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: MountDev (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: internal (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: BootIni (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: CopyPrivates (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: CreatePageFile (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: completion (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: RestartModule (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: ParseCommandLine (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: OnlineSettings (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: WpeUntndBtstrp (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: ModuleLoader (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: Ems (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: DiskInformation (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: license (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: LanguagePack (SEQ1)
  2016-04-14 20:45:12, info [0x0605a6] IBS requested UI to hide pages selection of language and regional settings.
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: space (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: locale (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: OnlineUI (SEQ1)
  2016-04-14 20:45:12, CallbackWin32UITerminate of the user interface of information: deleted WizardUI
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: Cmi (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: Sysprep (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: ProductKey (SEQ1)
  2016-04-14 20:45:12, IBS Info [0x06010d] Module_Term_Productkey: the valid product key in the table, see the property hide the value.
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: CBS (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: DynamicUpdate (SEQ1)
  2016-04-14 20:45:12, info [0x0500bd] of THE Module_Term_DU called
  2016-04-14 20:45:12, info [0 x 050081] of THE WaitAndCleanUp of THE...
  2016-04-14 20:45:12, info [0x0500a1] OF THE fact with THE... DUMgr cleaning
  2016-04-14 20:45:12, info [0 x 050082] with WaitAndCleanUp BECAUSE of THE...
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: LogTime (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: Unattend (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: UnattendImgInstall (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: CFGOfflineImage (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: ExternalDrivers (SEQ1)
  2016-04-14 20:45:12, info [0 x 090062] PANTHR destroying module: module IBS PnP (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: SystemRestore (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: ConfigSet (SEQ1)
  2016-04-14 20:45:12, info [0 x 090062] PANTHR destroying module: Source (SEQ1) media module
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: Imaging (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: MSDCleanup (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: CopySetupFiles (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: ComputerName (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: ScenarioDetect (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: engine (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: compliance (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: diagnosis (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: BootPrep (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: DiskConfig (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: TempDrive (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: FixBBPaths (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: FirstBootCleanup (SEQ1)
  2016-04-14 20:45:12, module Info [0 x 090062] PANTHR destroy: Rollback (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: UpgDriver (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: PrepareInstallDrive (SEQ1)
  2016-04-14 20:45:12, module to destroy the PANTHR Info [0 x 090062]: OnlineProgress (SEQ1)
  2016-04-14 20:45:12, info [0 x 090081] PANTHR destroying any source not cited modules! (SEQ6)
  2016-04-14 20:45:12, info [0x0601d7] IBS InstallWindows:Error Type = 3211266
  2016-04-14 20:45:15, info [0 x 090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  See you soon.

• STD R2 Windows Server 2012 was working fine this morning by restarting the server now, we get the error, choose your type of keyboard

  STD R2 Windows Server 2012 was working fine this morning by restarting the server now, we get the error to Choose your type of keyboard

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  See you soon.

• Upgarde Terminal CAL license question!

  Hi Tech team,

  I have a degree of CLIENT Terminal Server in addition to 50 users access licenses in windows 2003 std Edition. I have the w2k3 upgrded to win 2012 license terminal client access licenses it worked normally for more than 120 days. But I try to connect the RDP, its shows error connections. "

  Thank you

  VARUN

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  See you soon.

• error on Windows 2008 server std edition "Windows could not update the Configuration to start the computer. Installation cannot continue. "

  I try to install windows 2008 server std edition on HP DL 380 G5 server, I am getting error while installing "Windows could not update the Configuration to start the computer. Installation cannot continue. ", please suggest?

  I tried also with HP smartstart CD, but failed.

  Thanks guys, I found the answer to my question, I used the last HP smart Start CD (V8.70B for windows 2008 server X 64) for DL380g5 for windows 2008 server STD, and it worked fine.

  For the Smart Start CD list visit: http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=344318&lang=en&cc=nl&taskId=135&prodTypeId=18964&prodSeriesId=345557
  Thank you...

• NFS server crashes in Windows Server 2008 Std Edition

  Hello

  My problems together: -.

  1 NFS Client - Linux... Get in Windows Server 2008 Std Edition NFS server.
  2 NFS Client and Server services failed to restart.
  3 NFS Server crashes regularly and following several times to restart, windows all invited a blue screen with the message '' nfssvr.sys - address FFFFFA6006884051 base at FFFFFA600680C000. DateStamp A9939833 ".
  My question is:-
  1. is there a limitation of Windows Server 2008 Std Edition especially on the concurrent sessions of the NFS server?
  2. what could be the root cause of following services crash?
  3 NFS generates newspapers such as Windows Event Viewer system logs, etc.?
  Any feedback or help is much appreciated, because this issue is disturbing my entire web applications that take the source from the storage server.
  Thank you.
  Kind regards
  Wai Keong

  Hello

  Your question is more complex than what is generally answered in the Microsoft Answers forums. Please post your question in the TechNet forum. Check out the following link.
  http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer