I have a situation where, after upgrading to the most recent version of Windows 10, I'm only able to log into my Azure VM once. After I log in the first time, if my connection drops for whatever reason (which it's liable to do as my connection here is very unreliable) then I can't reconnect. I have to reboot the machine. I'm able to get past the login, however when I'm on the welcome screen it freezes and then I'm unable to do anything.
After a reboot, I can then connect successfully again until the connection drops, and then I have to reboot the machine.
The Windows version is "Windows 10 Pro N", build is 10.0.18362.
Previous to the upgrade I was able to connect multiple times with no issues.
Does anybody have any ideas what I could look for?
Thanks very much in advance,
Dave
In this case, I suggest installing the latest hotfix on https://support.microsoft.com/en-sg/help/4517389/windows-10-update-kb4517389
Or resize your Azure VM.
Hope this could help you.
Related
I keep running into this issue where when I try to save local app files from a Hololens to my computer via the Windows Device Portal, the Portal takes forever to download them and eventually times out. This is frustrating since I have no problem connecting to the Portal otherwise, and the files I'm trying to download are super small. Does anyone know of another way I can access these files?
WDP shows that it's waiting on the IP address for minutes before losing connection
How did you connect your HoloLens to the PC? With Wi-Fi or USB? To check if there are connectivity issues in your network, it is recommended that you try another connection method to access the Device Portal by following this doc:Using the Windows Device Portal. If the behavior still occurs, please open a support ticket through this link: http://aka.ms/hololenssupport so that we can diagnose it deeper for you.
I figured out my problem. I had the Hololens connected via USB yet was using the Device Portal as if I were connect remotely. To solve my issue, I had to use the address http://127.0.0.1:10080/ rather than the Hololens IP.
We're a software developer currently oferring a Cloud version of our software, hosted in a remote virtual machine. Our customers access this virtual machine via RDWeb, seeing (and working with) only the program.
Since the mentioned update (1083), our customers' computers running on Windows 10 are reporting a problem in which whenever they open a new windows in our software, that window is automatically moved to the background, behind other windows they may have opened in our software. That causes them to believe the program has crashed, and is seriously interfering with their line of work. The only common ground we've been able to find is the operating system (Windows 10) and that they had recently installed an update (specifically, the 1083 patch).
Has anyone had similar issues? If so, how have you managed to solve them?
Thanks in advance for your help and your patience
Jaime Peña
Kherian Soft, S.L.
I accidently broke my centos VM in azure by twiddling firewall rules within it. After a reboot, the normal ssh access is not working anymore. Is there any chance to get into that VM, any console login directly to the machine somehow?
After reading the current state (April 2016) at microsoft about this, I've decided to dump the virtual machine and set it up again:
This one-directional access is just a start. Console screenshots and serial output can help identify a problem, but they are not the solution for resolving the problems. We are working on enhancements that will enable secure bi-directional access to the console of the virtual machine. This will enable additionally debugging capabilities, and, more importantly, the ability to resolve a set of common problems through the bi-directional access. Right now, I don’t have a timeline but we know this is critical.
(article)
We've created a Windows 10 application that runs on tablets in Windows 10 kiosk mode. It works just fine, however, the wifi connection gets lost sometimes since the locations are very remote. We tried fixing the issue from the networking side, but when the devices lose and regain internet access the application will still hang as if it doesn't have internet access displaying a blank page. Where these devices are used, they are bolted into the wall to prevent theft. Which means if we want to reboot its very time consuming as we have to unscrew the cases off the wall and then open the cases to gain access to the power button, and the only way to get the application to run successfully again is to do a reboot on the device.
It was suggested that we have a way to perform a reboot from the application, however, every code example I've tried doesn't work in Windows 10 UWP. Here is the most common one I've found:
System.Diagnostics.Process.Start("restart", "/r");
I have access to the namespace
System.Diagnostics
but the Process class does not exist. Anyone have suggestions on rebooting via code on Win 10 UWP? Or a better solution to our issue? Thanks in advance.
It's also worth mentioning I tried execute a Powershell command too and the dll I need to reference for the Powershell class is not compatible with UWP.
What you require is not possible with the APIs available to UWP apps. This was a security decision. An app distributed through the store shouldn't be able to do things like restart machines.
Based on your scenario though you shouldn't need to go through the store. This means that you could PInvoke native code to do whatever you want. This would still need to be initiated on the actual device.
Yes you can do that!
You should add IoT System Administration in App capability declarations:
<Capabilities><iot:Capability Name="systemManagement"/></Capabilities>
and also You need to have "Windows IoT Extension for UWP" added to your project
using this for Shutdown
Windows.System.ShutdownManager.BeginShutdown(Windows.System.ShutdownKind.Shutdown, TimeSpan.FromSeconds(1)); //Delay is not relevant to shutdown
or for Restart
Windows.System.ShutdownManager.BeginShutdown(Windows.System.ShutdownKind.Restart, TimeSpan.FromSeconds(1)); //Delay before restart after shutdown
You can get more information in this Link
I tried to install a hardware I've installed in my previous computer under Windows 7, basically an external network card with antenna, but when I try to use it, after installed it I get this bluescreen error:
BUGCODE_NDIS_DRIVER
I don't know if it's possible to fix it, any useful information?
PS: If this isn't the best Stack forum, please guide me to the right one.
There is some technical information on Windows Dev Center - Hardware on this bugcheck. Driver developers can find the cause from the bugcheck code and parameters.
I can duplicate the BUGCODE_NDIS_DRIVER blue screen on my Windows 8.1 developer box fairly easily by opening two different VPN tunnels. Luckily, I don't need both running at the same time, so my solution is "don't do that".
For example, I open SonicWALL Global VPN Client to connect to one network. Then, I open the Cisco VPN client to connect to another. The crash happens almost immediately.
If you have two active network card, deactivate one, that is all.