Device Install Reboot Required Windows 10
I have just made a fresh (clean) install of Windows 10 x64 version 1709 and it is a total disaster. It is impossible to even install WMDC. Installer displays some useless message and that is all.Is there anybody who was able to at least install WMDC on Windows 10 1709?AndrewSOLUTION (ALL REQUIRED STEPS)My original question was about installing WMDC.
Alexander has given a perfect solution. Unfortunately there are a few more steps required to make it working. This thread is long and has a few references to other threads.
My system keeps telling me I need to restart my system to finish installing software for my device. I have already restarted multiple times. Restart Required Loop. Windows 10 restart loop in General Support. Since upgrading from win7 to win X, computer has been fine when on, shuts down ok for the night but when I come to start up next.
Below I will write a summary. Let'sassume you want to make a clean (fresh) install of Windows 10 1709. Personally I have tested these steps on Home and Professional x64 Polish version. Some texts are translated from Polish - it is possible that the same text in English Windows version has alittle different spelling.Install Windows 10 1709 and drivers required for your computer, connect to the internet and install updates.Install.NET 3.5. Select Programs and Features in Control Panel and then Turn Windows features on or off orca.msi file on your old computer.
It was installed as part of Windows SDK. If you don't have any read this: from Rune:Download ISO file from here and open it (Windows 10 can open ISO files, alternatively use 7-zip). Extract these files:Orca-x86en-us.msi838060235bcd28bf40ef7532c50ee032.caba35cd6c9233b6ba3da66eecaa9190436.cabfe38b2fd0d440e3c6740b626f51a22fc.cabInstall orca.Download Windows Mobile Device Center from here I'm using 64 bit version: drvupdate-adm64.exeUse 7zip to extract drvupdate-amd64.msi from drvupdate-adm64.exe. Read and work carefully. Do not confuse exe with msi.Open drvupdate-amd64.msi in orca and remove CustomAction MsiProcessDrivers.Save modified file and close ORCA.Install modified drvupdate-amd64.msi. The process should create c:windowswindowsmobiledrivers with 4 folders inside.Start the original drvupdate-amd64.exe and WAIT. There is no window or any other visible activity - installer works in the background.
You can observe the process in Task Manager or Sysinternals Process Explorer. Wait until:. CPU utilization is close to 0%. there is no drvupdate-amd64.exe process. there is only one msiexec.exeNow c:windowswindowsmobile should contain the complete installation.Open PowerShell or command prompt as Administrator and run these two commands:REG ADD HKLMSYSTEMCurrentControlSetServicesRapiMgr /v SvcHostSplitDisable /t REGDWORD /d 1 /fREG ADD HKLMSYSTEMCurrentControlSetServicesWcesComm /v SvcHostSplitDisable /t REGDWORD /d 1 /fRestart your computer.
Remember to be patient. Once I restarted my computer to early and the installation of drvupdate-amd64.exe was interrupted.Open Services (right click on Start, and then click on Computer Management = Services & Applications = Services) and find 'Windows Mobile-2003-based device connectivity' (WcesComm) and 'Windows Mobile-based device connectivity'(RapiMgr). You should see that both are working.
For both of them right click, select Properties and on Recovery tab in 'Subsequent failures' select the 'Restart Service'. Default option is to restart service after 1 minute.
I have changedit to 0. These modifications are required because both services are stopped when you disconnect your device.Run Windows Mobile Device Center program from Start menu.Connect your device to USB port.
Expected behavior: in the bottom right screen corner you should see that your device is being configured, a few seconds later device is ready, a few seconds later you should see in WMDC that device is connected.If you have any third party security software with firewall (I have ESET Internet Security) it is possible that your device will not connect to Windows Mobile Device Center.In default configuration firewall blocks communication for WcesComm service running in svchost.exe. Hi.I had the same problem and was able to install. To be sure that it works, could you please repeat what I did? I made following (on Windows 1709 x64 in Hyper-V):. Extract drvupdate-adm64.exe with 7zip.
There is two files inside: driver-setup.exe and drvupdate-amd64.msi. Using Microsoft ORCA, open drvupdate-amd64.msi and remove CustomAction MsiProcessDrivers: just delete the row. Save this file, close ORCA and then install it.
The process should create c:windowswindowsmobiledrivers with 4 folders inside. Start the original drvupdate-amd64.exe and WAIT. It will take 2-3 minutes (at least, so long took it on Hyper-v) until it finished. Sometime you will not see any activities, but it works in background.
Watch with Task Manager, until drvupdate-amd64.exefinished and the only one msiexec.exe is there. Now c:windowswindowsmobile should contains the complete installationI was able than in Hyper-V VM to install the Device Emulator, Windows CE 5.2 Emulator Image and connect over DMA (Enh.
Session should be off!)Please, let me know, if it works.Best regards, Alexander. Did you download the right version for your OS?Can you show what 'System Information' shows on your PC for 'OS Name' and 'Version'?I just did a clean install of:OS Name Microsoft Windows 10 ProVersion 10.0.16299 Build 16299And downloaded the 64 bit version from the page linked above (drvupdate-amd64.exe). Installing that results in:So, I contacted my support personnel (yeah, right!), extracted the exe using 7-zip and ran the installer msi with option /lv install.log:msiexec /lv install.log /i drvupdate-amd64.msiFrom the log we can see the following: MSI (s) (34:A8) 13:59:14:627: Invoking remote custom action. As a final attempt I tried to make a WIX installer out of the MSI. That almost works, apart from an ICE27 error I don't know how to fix.Using Dark.exe from the, and fixing several small items,(can't post it all here because the xml is too large).Unfortunately, building this results in the following error: WMDC.wxs(866,0): error LGHT0204: ICE27: 'RemoveExistingProducts' Action in InstallExecuteSequence table in wrong place.
Current: Selection, Correct: ExecutionIt seems to be caused by this part of the XML: NOT (REMOVE='ALL')NOT (Installed OR (REMOVE='ALL') OR (WpdPresent='1'))NEWPRODUCTFOUNDI'm hoping there is somebody on this forum with a good understanding of WIX/MSI that can help fix this issue. Maybe then we will be able to create a Windows 10 WMDC installer that actually works.Good luck,Michel Verhagen, eMVPCheck out my blog:GuruCEMicrosoft Embedded PartnerNXP Proven PartnerConsultancy, training and development services.Interested in WEC on i.MX6?Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here. Hi.I had the same problem and was able to install. To be sure that it works, could you please repeat what I did?
I made following (on Windows 1709 x64 in Hyper-V):. Extract drvupdate-adm64.exe with 7zip. There is two files inside: driver-setup.exe and drvupdate-amd64.msi. Using Microsoft ORCA, open drvupdate-amd64.msi and remove CustomAction MsiProcessDrivers: just delete the row. Save this file, close ORCA and then install it. The process should create c:windowswindowsmobiledrivers with 4 folders inside. Start the original drvupdate-amd64.exe and WAIT.
It will take 2-3 minutes (at least, so long took it on Hyper-v) until it finished. Sometime you will not see any activities, but it works in background. Watch with Task Manager, until drvupdate-amd64.exefinished and the only one msiexec.exe is there. Now c:windowswindowsmobile should contains the complete installationI was able than in Hyper-V VM to install the Device Emulator, Windows CE 5.2 Emulator Image and connect over DMA (Enh. Session should be off!)Please, let me know, if it works.Best regards, Alexander.
Windows 10 Shutdown Device Install Reboot Required
Hi Alexander,thank you very much for your idea. I can confirm that after following your procedure all services on my physical machine where installed and were able to start.I'm not at the office today so I cannot check the device connectivity but I will do that first thing in the morning. I get back to you with the results.BTW, MS Support's first response was 'Product is not supported on Windows 10 so we cannot put time into finding a solution'. But they want to discuss workarounds. We'll see.Best regardsUwe. Hi Uwe,I have installed the physical 1709 and connected per USB one MC9190, which I have here.
So, next 6 month until 1803 are safe now:)The issue is actually not with WMDC itself, but with AcLayers.dll - the SHIMS library. The background: Windows Installer MSIEXEC.EXE, which is in standard Windows delivery, is 'shimmed' with VistaRTMVersionLie. There is something wrong with theimplementation of this shim in 1709 AcLayers.dll in NSVistaRTMVersionLie::APIHookGetVersionExA - the stack overflow is happend in this function. I'm pretty sure, MS could easily solve it (I think, it is actually a bug)Best regards, Alexander. Well, for me this screen shows for about 30 seconds, then disappears and nothing happens. I tried uninstalling everything, reinstalling as per instructions by Alexander, but no joy.Note that the installation is indeed successful in the two-step approach.
The WindowsWindowsMobile folder contains the full installation now, but I just don't get WMDC to start on my machine.Good luck,Michel Verhagen, eMVPCheck out my blog:GuruCEMicrosoft Embedded PartnerNXP Proven PartnerConsultancy, training and development services.Interested in WEC on i.MX6?Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here.
Device Install Reboot Required Windows 10 Version
Hi to everyone,In our environment we have deploy some windows 10 enterprise 1607 10.0.14393We have wsus for deployment windows updates and sccm 1606 only for OS deployment.We have a gpo to download and install update at 04.00 PM (for example).Without any user loggedon, windows 10 download and install all updates, but don't restart as I'm expected.In previous test, some months ago, with the same GPO, it's works fine, if I remember correctly.The setting 'No auto-restart with logged on users.' Hi,Your configurations have some conflicts.Firstly, ' Always automatically restart at the scheduled time' policy conflicts with ' No auto-restart with logged on users for scheduled automatic updates installations'.
When 'No auto-restart with loggedon users for scheduled automatic updates installations' is enabled, 'Always automatically restart at the scheduled time' has no effect.In turn, since you have configured active hours is 08:00-20:00, you also schedule the installation time is16:00. In such conflict case, it never restart to complete the update.So here I suggest you:1. If you don't want restart when there is user sign in, please remain 'No auto-restart with logged on users for scheduled automatic updates installations' and remove 'Always automatically restart at the scheduled time' setting.2.
Specify the installation time in 'Configure Automatic Updates' out of the active hours and keep the computer on at that time.Please remember to mark the replies as answers if they help.If you have feedback for TechNet Subscriber Support, contact. Hi,In all cases nobody was logged on or with locked account:-(In the last test, patch was installed at 10.30 PM!!!! But restart never occur and message is that 'your device is scheduled to restart.bla bla bla. (active hours are 08.00 to 17.00)'ThanksAccording to your description, that's possible. You set the schedule install time is 12:00, it will not install at 10:30. And is your active time 1:00AM -2:00 AM or 08:00 to 17:00 on earth?Let's test as the follow steps:1. Open Task Scheduler, locate to Task Scheduler LibraryMicrosoftWindowsWindows Update, remove any task you specified.2.
Then set active hours.Then only (means no delay option like auto-restart with logged on users for scheduled automatic updates installations )set the 'Configure Automatic Updates' GPO for test.Note: make sure the installation time is not conflict with active hours.Please remember to mark the replies as answers if they help.If you have feedback for TechNet Subscriber Support, contact.