If you have a Windows 10 IoT Core device and want to change some basic settings, follow the instruction below.
First we need to set up a connection with the device
- Start Powershell (as administrator)
- First start the WinRM service by running: net start WinRM.
- Now run the following command: Set-Item WSMan:\localhost\Client\TrustedHosts -Value <machine-name or IP Address>.
Press ‘Y’ to confirm the change.
- Now start a session with the Windows 10 IoT Core device: Enter-PSSession -ComputerName <machine-name or IP Address> -Credential <machine-name or IP Address or localhost>\Administrator. As password use: p@ssw0rd.
|Change Administrator password
Remark: Once this is done, you’ll need to establish a new PowerShell session using Exit-PSSession and Enter-PSSession with the new credentials.
|net user Administrator [new password]|
|Change device name
Remark: You will need to reboot the device for the change to take effect
|Reboot device||shutdown /r /t 0|
I while ago I bought myself a Raspberry Pi 2 to play around with. I wanted it to run on Windows 10 IoT Core. That worked fine, with a display connected to HDMI. When the official Raspberry Pi 7″ Tochscreen Display came out I wanted to buy one immediately, but I was to late. The first batch was sold out :-). So I waited for the next batch and bought one.
I directly downloaded the latest version of Windows 10 IoT Core (build 10556), but the screen was not working. Using HDMI it was working…Argh. First I thought maybe the display is not properly connected, but when I tried Raspian, it work fine (even with touch).
I’ve let it rest for a while and today I picked it up again and found a forum post, stating that build 10556, wil not work with a v1.1 of the Rasberry Pi Display, but it will work with the latest preview build 14262. So assuming that I have a v1.1 of the display, I downloaded the preview version and yes, it’s working! Even with touch 🙂
Now the development can begin.
Having problems starting the Apache service on Windows 10? Probably port 80 is used by another process.
When you check which process is using port 80 (use Resource Monitor), it probably is the ‘System’ process (PID=4).
This means that a process by default installed and started by Windows is using port 80. Big chance that the ‘World Wide Web Publishing Service’ is running. Just stop it and set the Startup Type to ‘Manual’
Now try starting the Apache service again. If it is running, the Resource Monitor should now show that the ‘httpd.exe’ process is using port 80.
When you try to run Apache (or any other web server service), it can happen that Windows is not allowing to start it, because port 80 is already in use. To find out which process is using port 80, you can use the Resource Monitor (just run resmon.exe). Open the ‘Network’ tab and open the ‘Listening Ports’ section.
Another way to find out is to use ‘netstat -a -n -o | find “:80”‘.
How to solve the problem
If the process is just a ‘normal’ process, you just need to stop the associated service to free port 80. If it’s the System process (PID=4), that is using port 80, then we need to disable http.sys.
There are two ways to disable it:
- Go to device manager, select ‘View -> Show hidden devices’, go to ‘Non-plug and Play Driver -> HTTP’ and double click it to disable.
- Launch RegEdit, go to ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP‘ and change to value of ‘start‘ to 4.
After this you need to reboot your computer.
The following values are valid for the ‘start’ property: