I am getting the following error on a clean install, “There is not enough memory to complete the operation. To free up memory, close programs, projects, or windows you aren’t using, and then try again.” With Microsoft Project 2019 professional x64 under Windows 10 Enterprise x64 version 20H2 build 19042.1110.
I have tried the following (not necessarily in order) and I am never able to load the splash screen:
Reinstall office 2019 pro plus x64.
Reboot, then retry project.
Run project in safe mode.
Tried a different windows profile.
Tried Administrator.
I am completely out of ideas.
My system specs are as follows:
O/S: Windows 10 Enterprise x64 version 20H2 build 19042.1110.
CPU: i7 4930k
RAM: 64 GB
HDD Space available: 683 GB On a SSD.
The only thing I can even remotely think of is possibly the paging file. Which since windows was just barely installed, is non-existent.
Related
I initially tried to install haxm though android studio. Not working.
I downloaded the installer for haxm though intel. Not working because: VT-x is not supported by this computer or it is being exclusively used by Hyper-V.
But vt is supported and it's not used by hyper-v.
I checked windows feautures and all hyper-v options/suboptions are off. I checked windows defender -> core isolation -> memory integrity and it's off. I have no other antivirus software that could possible block hyper-v, I have only windows defender.
I tried turning off, in case it's on, with command line and then rebooted and tried installing again.
I checked the bios/uefi and vt is enabled, mts (multithreading) is enabled.
I checked windows services and there was no service, relative to hyper-v, running.
I don't believe that there might be another software running in the same time which causes this problem (like amd driver (andrenaline), asrock rgb, or I don't know what).
Any idea?
CPU : ryzen 5 2600. MOBO: Asrock Fatal1ty B450 Gaming K4. OS: Windows 10 Education (latest version)
(I am not sure if this post fits here but I have seen a couple of posts regarding installation problems of HAXM. I read them. Still, they're not helpful for my problem as it seems)
Do check the following things
go to BIOS of your system, if your system (laptop/desktop) have intel processor then enable the VT-X (virtualization technology).
if your laptop/desktop have AMD processor then enable HYPER-V form your BIOS.
This will fix your problem for sure. If not then try to update your BIOS.
Fixed it having the following settings:
Under advanced/cpu settings:
SVM enabled. MTS enabled.
Under advanced/northbridge:
SR-IOV enabled.
On windows:
Hyper-V off. Windows Hypervisor on.
On windows defender:
Core Isolation -> Memory Integrity: off
On android studio:
Settings/System Settings/Android SDK:
Android Emulator On
Android Emulator Hypervisor Driver for AMD Processors On
(Check running services for related tasks. Check 3rd party software)
Reboot.
Don't try to install Intel x86 Emulator Accelator(HAXM) with AMD. There is no way to do it with AMD.
We're in the process of converting our two FoxPro systems to new technology, but meanwhile we need to upgrade our server and I am trying to find out whether our legacy systems will run there. We'd prefer to go to Windows Server 2019, but using Server 2012 is possible. Our stations are Win 7 or 10 Pro, some 64-bit.
One system is in Visual FoxPro 9 and uses its native DBFs and some DBFs in FPD 2.6 format. Certain graphical and document functions (e.g.: OCR) are performed by calls to LeadTools 12.0. The application also calls Outlook.
The second system is a single-user application in FoxPro for DOS 2.6 run from an .app file. The 32-bit stations run this natively, while the 64-bit stations use the product, vDOS, to allow the 16-bit FPD to run there. The application wants to reside on the server since multiple stations can run it, albeit at different times.
Any help is much appreciated. Thank you!
Will a Visual FoxPro 9 EXE run on those server operating systems? Yes.
Will a Foxpro For DOS or FoxPro for Windows EXE run on those server operating systems? No. Those flavours of FoxPro are 16-bit, and as such would require a 32-bit version of Windows Server, the last of which was Server 2008.
However I suspect you are not running either of these on the server. You have a shared folder on the server with the DBFs in it, and the executables are running on workstations.
So if you have a 64-bit OS on the workstation then you can only run the Visual FoxPro exectuable directly. If you had a 32-bit OS on the workstation, you can run both Visual FoxPro and FoxPro for DOS\Windows executables.
Your question is really 'can I put the DBFs in a shared folder on those server operating systems and access them from client workstations?', and yes you can.
I am wrestling with an issue I cannot understand. We have a ClickOnce deployment of a WPF application in Azure blob storage. The processor architecture is everywhere "msil" in this deployment. When it gets run from IE, it runs as a 32bit application on AMD64 computers. The desired behavior would be to run as 64 bit. Could someone please enlighten on where should I look to fix this problem?
I already managed to go through the hoops to build the assemblies as x64 and create the ClickOnce deployment as amd64. This combo will run as 64 bit. The desired behavior is to still have it "msil" so it can run as either 32-bit or 64-bit, depending on the operating system it will be running on.
I'm currently using VS11 beta in a VM but its far to slow and it has crashed. But I was also installed under windows 8 which i found slow so i'm not sure if the speed problems is related to windows8+running in VM or if the produce is also slower.
Is VS11 beta stable on windows7? Does it crash often? (it crashed multiple times for me under windows8 in a vm). Will i have problems developing .NET 2-3.5? Can i have a duel install with 2010 + 11beta?
What should i know before installing the beta on my main machine?
It appears to be very stable.
Personally, I've been using it on Windows 7 for quite a while now (from pre-beta) and have had zero crashes. I've also used it in Windows 8 and haven't seen any speed issues (both bootable VHD and a VirtualBox VM). Your experience may be different.
You can run VS2010 and VS11 side by side. If you have VS2010 SP1 installed projects can be round-tripped so that after you upgrade the project in VS11 it will still work in VS2010.
Working on .NET 2.0 and above is supported.
I have a vdi file that is using Windows Server 2008 R2.
Each time I try to start it, I get this message:
http://i.imgur.com/zx5bp.png
It would then display a "Windows is loading files..." page and repeatedly loops the message:
http://i.imgur.com/xsywH.png
My Laptop Specs:
Processor - Intel Core 2 Duo T6500 2.10GHz
RAM - 4 GB RAM
OS - Windows 7 Pro 64 bit
Virtualbox Guest OS:
Base Memory - 512 MB
Video Memory - 32 MB
Not sure what to do. I pretty much searched through all of Google and can't seem to find an answer or any tutorials related to this issue.
Any information or advice would greatly be appreciated.
Thank you
usually this error is occured when you try to configure your VDI image for any incompatible OS architecture selection.
for eg: VDI file is of Windows 7 32bit, but you are tyring to configure this using a Windows 764bit option.
The best solution to overcome this is to use the "Export Appliance" option from file menu and then, "Import Appliance". Benifit is, the wizard automatically identifies which OS architecture it was originally configured for.
Problem solved. The Intel Core 2 Duo T6500 mobile processor does not support 64-bit Guest OS.
Below is link for anyone interested
http://ark.intel.com/VTList.aspx