Cannot Install Rhino7 on Windows 10 Home

Hi, I downloaded Rhino7 for Windows, “rhino_en-us_7.1.20343.09491.exe” and I run it on a Windows 10 Home Edition.
But nothing happened. I think the installer keeps crashing after opening.

  • my Windows10 Home is current version.
  • I can use Rhino6 on the Same machine.
  • The installer could run on another PC(windows10 pro x64).

Any suggestions?

Is it possible that your Win 10 Home is 32-bit? Rhino 7 only runs on 64-bit.

If you have an antivirus tool running, please disable it before you run the Rhino installer.

Any luck?

Thanks,@AIW. But my win10 Home is 64bit.

Thanks @John_Brock
But I had run the installer, after stopped an anti-virus software.
And my another PC which is running on win10 pro and the same anti-virus app can run the installer.

I upgraded OS from Windows10 Home 64bit to Windows10 Pro 64bit today.
*My OS is Windows 10 Pro, Version 20H2, OS build 19042.685

And redownload and re reinstalled “rhino_en-us_7.1.20343.09491.exe” , But nothing happened.
I can’t understand what is happen.

Event Viewer log is here.

Log Name: Application
Source: Application Error
Date: 2020/12/21 11:31:32
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: SOUPNOTE
Description:
Faulting application name: rhino_en-us_7.1.20343.09491.exe, version: 7.1.20343.9491, time stamp: 0x5e1a1465
Faulting module name: BundleUI.dll, version: 1.0.0.1, time stamp: 0x5fcfdf22
Exception code: 0xc0000005
Fault offset: 0x00002b46
Faulting process id: 0x551c
Faulting application start time: 0x01d6d741648c325c
Faulting application path: C:\Users\soups\AppData\Local\Temp{941A7213-CFDC-4744-94E1-87DC971EF09C}.cr\rhino_en-us_7.1.20343.09491.exe
Faulting module path: C:\Users\soups\AppData\Local\Temp{1ED89B42-56A2-409B-BB4F-543B85E110D5}.ba\BundleUI.dll
Report Id: 18651a32-8f53-4ab4-abf9-3f95e77a805a
Faulting package full name:
Faulting package-relative application ID:

What should I do?

Did you have a solution to this problem? Having the smae problem right now.

@John_Brock was there a different solution?

@John_Brock Also having the same problem, Any other ideas?