Re: Virtualbox 64-bit Windows 7

0 views
Skip to first unread message
Message has been deleted

Roseanne Gennett

unread,
Jul 10, 2024, 4:50:08 PM7/10/24
to cawelcongte

I have downloaded and installed the newest virtualbox 4.3.20 for my Windows 7 (64-bit OS), but when I want to install 64-bit Linux, the New->Create Virtual Machine only displays 32-bit option, no 64-bit option. Could anyone give any clues about this issue? Thanks very much in advance!

virtualbox 64-bit windows 7


تنزيل الملف https://urluss.com/2yZalj



If you want to emulate 64 bit apps on a 64 bit host, your cpu needs a feature for that. Which duDE says, is an intel-specific copy-paste. The same support exists on AMDs too, there its name is AMD-v - maybe he forgot to mention.

Had the same problem, only seeing 32-bit versions for the host OS's. Started working after updating asus p8z77-v pro bios to latest and enabling virtualization support. Before the bios update, virtubox showed only 32-bit OS's.

Using the guidance in the answer by @Leo Chapiro I was able to install Debian Buster 10 with Gnome on Windows 10 on a Lenovo ThinkPad. Here's the step-by step way I enabled the 64 bit option in VirtualBox:

We have a program that needs to run on Windows XP 32 bit. The host is windows 7 64 bit. The Xp is running on Oracle Virtual box and the old printer that used to work died. Now the issue is trying to get the printer from the host to install on virtual box and print. Anyone with the same issue can give some insight the new printer is an HP envy 5540 all-in-one

yes it is a locally connected via USB to the host. I would have used XP mode but I did not install it, this happened well before me the program is a legacy windows 3.1 program. No errors just does not print sits in the queue and then eventually says it cannot print .

Can you map the printers on the XP host? net use LPT1 and the printer path. That is what I did with running a 16 bit DOS application on Win 7 64 bit. Mapped the printer with the command prompt on the virtual XP machine.

If the old printer died, and all you did was change printers, then the old printer likely has a specific configuration - either on the host, or through virtualbox - that you are not replicating properly when you connected the new printer.

1- Make sure File and Printer Sharing is enabled fully on the host.
2- Install and share the printer as LOCAL / USB connected at the HOST using the correct Windows 7 driver. Being an HP AIO Printer, this means install the software first, then connect hte USB. Do not try and install the XP drivers.

Since the original post the software is being updated to web based so by the end of the year the Oracle Virtual box will be uninstalled. In the meantime the user is using the Windows 7 Snipping tool to print his reports. Not perfect but we determined that no point spending time and energy on a program that is going to the big deleted bin in the sky

After updating Virtualbox and installing guest additions for the new version on a Windows 7 guest, the guest additions no longer start and the functionality provided by them no longer available (specifically, shared folders and mouse).

To eliminate the possibility that this is a Windows issue vs. a host/VBox issue, what happens you restore the guest from snapshot and roll back the virtualbox update? Be sure to roll back ALL VBox related packages to their previous version.

There are plenty of open bugs listed at VirtualBox Open tickets (Windows guests only) for Windows 7, for example, the "verify digital signature" one is mentioned several times, so I doubt this is a packaging issue. It might be time to ditch Windows 7, which has been out of support/patches for over 3 years.

Same here, with Win7 guest. On guest boot there is possible to press F8 and tell Windows not to verify signature. After that guest boots and additions works as intended.
Wrong signature already reported on the Virtualbox site, hope it will be updated soon.

As you mentioned, it works on a dkms, why are you running a regular virtualbox then? Which linux kernel are you currently running?
Is this a 32-bit Windows 7? If it is, then it is in conflict with the 64-bit addition you installed.

03c5feb9e7
Reply all
Reply to author
Forward
0 new messages