It's not working, installed WES7 toolkit with WEDU, copied the user.config to C:\Users\Administrator\AppData\Local\Microsoft\WEDU\ then ran the WEDU it just says to register the product..
%appdata% is in "Roaming", not "Local" (you may need to create the Microsoft\WEDU folder if it doesn't exist).
Hello, i installed the Windows Embedded Standard and i started the WEDU. i got the info "No supported products detected". What make i wrong? Can it be due to the German version? Best regards
Hello, thanks for your answer. Yes, i got run the WEDU in the installed OS. I read the first post again, also i translated in german but i not understood. I looked the video on he MS-page about WEDU. Do I need to extract the WIM file? I have no idea. Would be grateful for a step-by-step instructions. Best Regards
It doesn't work that way. To use WEDU you need to have the WES7 Toolkit installed, and a WES7 distribution share. These are usually installed on another OS, not in a WES7 installation. If you just want to update a WES7 installation you can't use WEDU, and you should use Windows Update.
Hello 100, thank you for your note. i installed the Toolkit and a Distribution share via the "Image Configuration Editor". I copied your user.config to Administrator\AppData\Roaming\Microsoft\WEDU. If i start the WEDU now is on the left side "Unregistered Products" - "Windows Embedded Standard 7". Best Regards,
Hello, i have the user.config loaded again and copied into the folder. Now everything works. Best Regards,
ok but during setup procedure, Is request uninstall the WEDU because WES8 Toolkit need installed a new version.. !! if accept uninstall of previous version .. WEDU work correct again ( without insert "old user config files " ) ??
hi, I have installed wedu 2.0 , ICE7 work correctly, but ICE WES8 show 30 day of trial version ... it's possible remove trial period ? Note: WEDU Update show error "impossible connect to server"
Yeah, it's no longer connecting to the server. Used this a few months ago and it did not seem to have any problems. Apparently it's a DNS resolve problem on Microsoft's side. If someone knows the correct IP address for the Embedded update server, this can probably be manually entered in Windows's Hosts file or WEDU's config. Otherwise, we'll just need to wait: social . msdn.microsoft.com/Forums/en-US/66369b66-ebeb-4b59-8e32-e980aed63645/windows-embedded-developer-update-12?forum=quebecservicingdeployment