I am running ubuntu on top of windows 10, hyper-v. Everything goes fine but if I lock my laptop even for sometime, time inside ubuntu becomes out of sync with windows machine. I tried various ways like "chronyd" sync etc but nothing works. Things return to normal, if I restart hyper-v container; but it is painful as I need to start all work again from scratch.
I found a fix for this issue without restarting hyper-v container (ubuntu, in this case). Here are the steps:
Open your hyper-v Manager application.
select the container which is having time issue.
right click on it and select "settings".
Select "Integration services" now, this will show "Time synchronization" check box like this
uncheck that box and click "apply" button. Now again check that "Time synchronization" checkbox and hit "apply" button.
Correct time appears inside container.
Related
I have a Windows10 Azure Virtual Machine running, and via the Windows Update Config screen (in Windows) I see several updates ready to install. However, the Update and Restart option in the start menu doesn't seem to do anything, and the same for the Restart functionality in the Virtual Machine pane of Azure.
I created an Update Management schedule (via Guest & Host Update menu), but this also doesn't seem to do anything. It succeeds after one minute, and when I look on the VM it still lists the updates as needed to install.
How can I install these updates on a Windows10 Azure Virtual Machine?
Try following the steps in this article to clear the Windows Update Cache. Then attempt installing one at a time
https://blogs.technet.microsoft.com/mckittrick/windows-update-issues-clear-windows-update-cache/
If that fails, please try the following :
Click on Start, and then click Run.
Type cmd in the Open box to get a DOS prompt.
Type "net stop wuauserv" without the quotes at the command prompt, and press
Enter.
Delete (or put in recycle bin) the contents of
C:\WINDOWS\SoftwareDistribution (but not the SoftwareDistribution folder)
Type net start wuauserv at the command prompt, and press Enter.
Now try Windows Update again.
If the issue still persists, kindly share the screenshot of the windowsupdate
Also is this the only VM where the issue is happening?
This is my screenshoot for Next Button not turn on when i am trying to create Virtual Device in AVD Manager but system image cannot be selected and next button not turn on.
I am running Android Studio using 32bit computer with 1GB RAM and everything is okay, except its AVD Manager cannot be selected system image. Do you know what should i do, so the Next Button on this image below can turn on?
I think I found the problem - expand the column where the names of the images are - then, all of the sudden the "download" link appears.
Go through the download process and accept the license if you have to.
and it should work from there.
Stupid idiotic problem to have, found the solution by accident.
You should be having at least 4gb RAM.
When apps crash, Windows used to popup a dialog box saying {Program} has stopped working with a Close button. I no longer see this dialog box on Windows 10. How do I get it back?
I thought perhaps I messed up some registry setting, so I downloaded a Windows 10 VM from Microsoft, crashed a program in the VM and I still didn't get a dialog box. So there must have been some change to Windows.
I tried tweaking the AeDebug registry key, but still couldn't get the dialog box back.
The reason I like the dialog box is because it tells me right away that some program has a problem that I can investigate further.
As described here, you need to set the Windows Error Reporting setting DontShowUI=0 with the Registry Editor or Group Policy Editor.
sounds a little dumb when i tell that but, when app stops working for me i usually press the left mouse button a lot in the windows (of the app) until it will display the message to end the process
Everything used to work fine, but I haven't been using Virtual Box for several weeks. Now all of the sudden, I get the following exception when trying to start my Windows 10(32-Bit) VM. Note - Things were working fine several weeks ago. As far as I can tell, I haven't changed anything on my system that would cause this. The exception details are as follow:
VirtualBox - Error In supR3HardenedWinReSpawn (rc=-5640)
Please try reinstalling VirtualBox. where supR3HardenedWinReSpawn
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification
Failure: The process has more than one thread
I have been researching this for some time, to avail. Any help would be greatly appreciated.
There is a workaround:
Open VMbox manager
Run your VM with option "Detachable start"
Wait a while and then use "Show" to show the screen
Detachable start option
Show the screen
My setup:
Oracle VM Box 6.0 running on Win10,
VM is Ubuntu 18.04
If you are using vagrant to boot up your Virtual machine, then in most cases the error is due to improper shutdown of the VM. A fix that worked for me is to execute vagrant halt or similar commands multiple times until you have a clean boot.
In case anyone is in the same predicament, I will share what finally fixed my issue. I found a post during my hours and hours of searching that said you have to enable virtualization in BIOS settings. I checked my machine and virtualization was enabled, so I went on searching. At a loss for what to try next, I finally tried turning virtualization off, just to see. No change, but when I went to turn it back on, just as a flook I turned Turbo off, and what do you know - All of the suddent I can start my VM. So the solution, in case it saves someone time:
Uninstall Virtual Box (Latest Version)
Reboot your machine and enter BIOS
Make sure anything with the term 'Virtualization' is turned on
Make sure anything with the term 'Turbo' is turned off
Reboot your machine
Install Virtual Box
Hopefully this saves some poor soul what I had to go through to get this thing working.
METHOD A
If you are using WindHawk, exit it and re-try.
Method B
download previous version from https://www.virtualbox.org/wiki/Download_Old_Builds
install & extensions
Try to re-run your guest OS.
Try to do these steps:
1. Uninstall the VirtualBox program.
2. In your C:\users\\ might have two folders called ".VirtualBox" and "VirtualBox VMs": Delete them
3. Restart your PC
4. Install VirtualBox again
5. Add again your VM
6. It must working fine!
These steps worked for me!
Workaround 1:
Just increase the RAM size from virtual box settings
Right Click on OS image .
Settings->System->MotherBoard
Increase the base memory
Workaround 2:
Change the Paravirtualization Interface from default to none
Right Click on OS image .
Settings->System->Acceleration
Change acceleration from default to none.
The above one's was basically a workaround , which can work in some but not in all.
The best thing would be to reinstall virtual box with latest version which virtual box has tried to rectify the bug and use the same vdi files which was made by Virtual Box .
One of the most common causes that will cause this type of behaviour is a missing driver (VBoxDrv.inf). It’s possible that due to some permission issues, the installation of this crucial driver doesn’t complete during the initial installation. In this case, you can fix the problem by installing the VBoxDrv.inf manually.
1.Fix the directory problem Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘regedit’ and press Enter to open up Registry Editor. When you’re prompted by the User Account Control (UAC), click Yes to grant admin access.
Once you’re inside the Registry Editor, use the left-hand section to navigate to the
following location: HKEY_LOCAL_MACHINE\system\currentcontrolset\services\vboxdrv
After you arrive at the correct location, move over to the right-hand section and
double-click on ImagePath the path associated should be \C:\Program
Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.sys
if not replace with the above path and click ok.
Install the VBoxDRV.inf OPen location C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv right-click on VBoxDrv.inf and choose Install from the context menu.
Then in cmd run command "sc start vboxdrv"
Restart system. This should work.
I'm happily using x2go to connect to a remote Ubuntu Server 16.04 with XFCE installed from my local pc with a local resolution of 1920x1080 on a HiDPI screen (13''). If I run the x2go client from a virtualized Linux (Linux Mint 18.03 with XFCE), everything works well and I can see a really sharp image of the remote desktop. Problem is, when I try to connect directly from Windows 10 the image is blurred and the resolution is wrong. I tried to play around with the x2go client settings but no way, the image is always terrible. I also tried to use PyHoca and different X-servers but the result is the same.
Is it a well-known problem? Any suggestion on how to fix it?
Thanks in advance.
I had a very similar problem: A Dell laptop with an Nvidia graphics card, having a resolution of the built-in flat panel of 1280x800. I connected this to an external screen with HDMI with a resolution of 1920x1080. However, X2Go seemed to pick up the resolution of the built-in screen instead of the actual screen, making everything seem blurry (interpolating 1280x800 to 1920x1080).
This is what fixed it for me: Navigate to the C:\Program Files (x86)\X2GoClient\VcXSrv\ directory in Explorer. Select the vcxsrv.exe file and right-click it, choosing Properties from the popup menu. Go to the Compatibility tab, and in the Settings section there, select the option "Override high DPI scaling behavior. Scaling performed by:" and then select "Application" in the combo-box below.
Restart the X2Go Client to have its X server start with this new setting.
This fix also solved X2Go Windows Client crashes in my setup.
I have basically the same scenario: connecting from a high DPI Windows laptop to KDE on Debian, in my case for Desktop Sharing. The client would connect okay, but display only a portion of the remote host's screen.
Keyboard shortcuts would not scroll the client window.
Any attempt to show more (maximize, go full screen, click-and-drag client window border) would seem to work for a second, then crash.
The Compatibility scaling change fixed the instability - no more crashes, yay! - but did lead to slow repaints as noted by Algeboy.
Upgrading to a newer version of VcXsrv also did not resolve the crashes - Compatibility change still required, but screen repaints are quicker.
To upgrade, download and install the latest VcXsrv in its own directory. Using Explorer or whathaveyou, apply the HiDPI setting to vcxsrv,exe.
Start x2go client but don't start a session. Click Options, Settings, then X.Org Server settings tab. Select "use custom x server". Point to the newly installed vcxsrv.exe and click okay. Restart the x2go client.
This apparently takes the version from 1.20.6.0 supplied by x2go to 1.20.14.0 (2022-04).
Screen refreshes are quicker if I minimize all applications on the host, allowing it to repaint the desktop, then restore whatever I want to work on.