AS7735Z

Germain
Germain Member Posts: 9 New User
edited March 2023 in 2017 Archives

Can not run Blender 3D under Windows 10

Answers

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    What was the factory-installed Windows version? Try running it that compatibility mode. Jack E/NJ

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    It does not solve the problem, says it is missing the open GL 2.1 graphics driver

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    You should try to download and install the latest blender version 2.78C compatible with Win10 from this link.

     

    https://www.blender.org/download/

     

    Jack E/NJ

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    I got that version, anyhow uninstalled .msi, reinstalled, same problem

    tried the 32-bit, same problem

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    What errors or warnings does Device Manager reveal? Jack E/NJ

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    Device manager does not show any problem

     

    Opening Blender messages:

    Legacy WGL is unable to select between OpenGL version

    Blender requires a graphic driver with openGL 2.1 support

     

    Before switching to Windows10, it was OK on Vista Home Premium

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    Did you run the Win10 compatibility app ***before*** switching to Win10 to see if your graphics adapter would work properly? Jack E/NJ

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    Not sure, but all other programs sofar are OK

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    Go back to Device Mgr. What display adapter is listed cuz there were 4 possible used in your model. Since all these adapters are ~10 years old and designed for a ~10 year old Windows version, their hardware drivers may not have been updated to work properly with ***all*** applications & programs, especially graphic-intensive ones, like 3D under Win10. Nevertheless, we can try to see if yours has been or can be updated to support the openGL driver under Win10. But we have to know what model is from Device Mgr. Jack E/NJ 

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    Mobile Intel(R) 4 Series Express Chipset Family (Microsoft - WDDM 1.1)

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    As of about a year ago, an openGL driver for this older Intel adapter simply wasn't available for Win10. This resulted in common Win10 incompatibility issues for many graphic-intensive programs like 3D that needed this driver to run properly. However, this situation may have recently changed. So I recommend that you go to this Intel site below to automatically detect what updates, if any, are now available for your adapter and other Intel components.  Let us know the results one way or the other.

     

    http://www.intel.com/content/www/us/en/support/detect.html

     

    Jack E/NJ

     

     

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    thanks for all, had done this a few days ago, reinstalled now the Intel utility, updated to 10.1.1.14

    however, no succes

    fyi, unity and gimp are running perfectly (hobbyist)

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    OK. Then I'd try again in different compatibility modes. WinVista, WinXP, Win7, Win8, Win8.1. If none of those modes bring any joy, I think you have at least 3 options, maybe more. The first I'd try if you haven't done so already, is join one the blender user groups and post the issue with your particular graphics adapter.

     

    The second is the route I've taken with BOTH uncooperative hardware & software that don't wanna play nice with newer Windows or Linux versions. I run them under a free or modesltly-priced VMWare player as virutal machines. Right now I have WinXP, Win98SE, Win95, Win7 & SuSE Linux all installed on the same laptop. It's possible to run all at the same time with all internally networked to each another to transfer workfiles from one OS environment to another.

     

    The third is to Alt+F10 back to factory-fresh WinVista if your hidden Acer recovery partition on the HDD is still intact. The problem here is that, unless you made a backup, you'll have to re-install all your previous personal software that wasn't factory pre-installed.

     

    Jack E/NJ     

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    1. done, tried several suggestions, no succes

    2. have no experience with VM

    3. not possible anymore

    many thanks for all your time

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    One last 2 things to try if you haven't done so already. Go back to Device Manager and right click on your display. Then have Win10 automatically search for an updated driver via the internet if you're connected. If that doesn't work, you can uninstall the existing adapter and its driver from Device Manager. Exit Device Manager. Do a cold re-boot and let Win10 re-dectect the adapter and re-install what it ***guesses***  is the best driver for the adapter. Maybe it'll work. Maybe it won't. Your decision on whether or not to give it a shot. Jack E/NJ     

    Jack E/NJ

  • Germain
    Germain Member Posts: 9 New User

    fyi, noticed that the Intel update did not install at all, added the logfile here:

    [0DE4:24C4][2017-03-19T17:47:43]i001: Burn v3.7.1224.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\germa\Downloads\Intel Components\SetupChipset.exe, cmdline: '-burn.unelevated BurnPipe.{74DD7599-4925-4A6F-B347-504F783A65B1} {596E4A6E-3658-4A16-8768-069D0DA51DB1} 7480'
    [0DE4:24C4][2017-03-19T17:47:43]i000: Initializing string variable 'IIF_ProductVersion' to value '10.1.1.14'
    [0DE4:24C4][2017-03-19T17:47:43]i000: Initializing string variable 'IIF_InstallerVersion' to value '3.1.6'
    [0DE4:24C4][2017-03-19T17:47:43]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx86.msi' to value ';NullDrivers.cab;NOT VersionNT64'
    [0DE4:24C4][2017-03-19T17:47:43]i000: Initializing string variable 'IIF_ExtractionMapping_SetupChipsetx64.msi' to value ';NullDrivers.cab;VersionNT64'
    [0DE4:24C4][2017-03-19T17:47:46]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\germa\AppData\Local\Temp\Intel\Logs\Chipset_20170319174746.log'
    [0DE4:24C4][2017-03-19T17:47:46]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\germa\Downloads\Intel Components\SetupChipset.exe'
    [0DE4:24C4][2017-03-19T17:47:46]i052: Condition 'VersionNT >= v6.1 OR (VersionNT = v6.0 AND NTProductType = 3)' evaluates to true.
    [0DE4:24C4][2017-03-19T17:47:46]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'
    [0DE4:24C4][2017-03-19T17:47:46]i000: Loading managed bootstrapper application.
    [0DE4:24C4][2017-03-19T17:47:46]i000: Creating BA thread to run asynchronously.
    [0DE4:1D0C][2017-03-19T17:47:46]i000: ** MBA ** Command line:
    [0DE4:1D0C][2017-03-19T17:47:46]i000: Setting string variable 'WixBundleName' to value 'Intel(R) Chipset Device Software'
    [0DE4:1D0C][2017-03-19T17:47:46]i000: ** MBA ** Calling Engine.Detect()
    [0DE4:24C4][2017-03-19T17:47:46]i100: Detect begin, 3 packages
    [0DE4:24C4][2017-03-19T17:47:46]i000: Setting string variable 'DotNet35' to value '1'
    [0DE4:24C4][2017-03-19T17:47:46]i000: Setting string variable 'DotNet40Client' to value '1'
    [0DE4:24C4][2017-03-19T17:47:46]i000: Setting string variable 'DotNet40Full' to value '1'
    [0DE4:24C4][2017-03-19T17:47:46]i000: Setting string variable 'DotNet45' to value '394802'
    [0DE4:24C4][2017-03-19T17:47:46]i052: Condition 'DotNet35 OR DotNet40Client OR DotNet40Full OR (DotNet45 >= 378389)' evaluates to true.
    [0DE4:24C4][2017-03-19T17:47:47]i101: Detected package: DotNet45, state: Present, cached: None
    [0DE4:24C4][2017-03-19T17:47:47]i101: Detected package: SetupChipsetx86.msi, state: Absent, cached: None
    [0DE4:24C4][2017-03-19T17:47:47]i104: Detected package: SetupChipsetx86.msi, feature: NullDriverFeature, state: Absent
    [0DE4:24C4][2017-03-19T17:47:47]i104: Detected package: SetupChipsetx86.msi, feature: PackageVersionFeature, state: Absent
    [0DE4:24C4][2017-03-19T17:47:47]i104: Detected package: SetupChipsetx86.msi, feature: LicenseAgreementFeature, state: Absent
    [0DE4:24C4][2017-03-19T17:47:47]i101: Detected package: SetupChipsetx64.msi, state: Absent, cached: None
    [0DE4:24C4][2017-03-19T17:47:47]i104: Detected package: SetupChipsetx64.msi, feature: NullDriverFeature, state: Absent
    [0DE4:24C4][2017-03-19T17:47:47]i104: Detected package: SetupChipsetx64.msi, feature: PackageVersionFeature, state: Absent
    [0DE4:24C4][2017-03-19T17:47:47]i104: Detected package: SetupChipsetx64.msi, feature: LicenseAgreementFeature, state: Absent
    [0DE4:24C4][2017-03-19T17:47:47]i199: Detect complete, result: 0x0
    [0DE4:24C4][2017-03-19T17:49:05]i200: Plan begin, 3 packages, action: Install
    [0DE4:24C4][2017-03-19T17:49:05]w321: Skipping dependency registration on package with no dependency providers: DotNet45
    [0DE4:24C4][2017-03-19T17:49:05]i052: Condition 'NOT VersionNT64' evaluates to false.
    [0DE4:24C4][2017-03-19T17:49:05]i204: Plan 3 msi features for package: SetupChipsetx86.msi
    [0DE4:24C4][2017-03-19T17:49:05]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
    [0DE4:24C4][2017-03-19T17:49:05]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
    [0DE4:24C4][2017-03-19T17:49:05]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
    [0DE4:24C4][2017-03-19T17:49:05]i052: Condition 'VersionNT64' evaluates to true.
    [0DE4:24C4][2017-03-19T17:49:05]i204: Plan 3 msi features for package: SetupChipsetx64.msi
    [0DE4:24C4][2017-03-19T17:49:05]i203: Planned feature: NullDriverFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
    [0DE4:24C4][2017-03-19T17:49:05]i203: Planned feature: PackageVersionFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
    [0DE4:24C4][2017-03-19T17:49:05]i203: Planned feature: LicenseAgreementFeature, state: Absent, default requested: Unknown, ba requested: Unknown, execute action: None, rollback action: None
    [0DE4:24C4][2017-03-19T17:49:05]i000: Setting string variable 'WixBundleRollbackLog_SetupChipsetx64.msi' to value 'C:\Users\germa\AppData\Local\Temp\Intel\Logs\Chipset_20170319174746_0_SetupChipsetx64.msi_rollback.log'
    [0DE4:24C4][2017-03-19T17:49:05]i000: Setting string variable 'WixBundleLog_SetupChipsetx64.msi' to value 'C:\Users\germa\AppData\Local\Temp\Intel\Logs\Chipset_20170319174746_0_SetupChipsetx64.msi.log'
    [0DE4:24C4][2017-03-19T17:49:05]i201: Planned package: DotNet45, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
    [0DE4:24C4][2017-03-19T17:49:05]i201: Planned package: SetupChipsetx86.msi, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None, cache: No, uncache: No, dependency: None
    [0DE4:24C4][2017-03-19T17:49:05]i201: Planned package: SetupChipsetx64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
    [0DE4:24C4][2017-03-19T17:49:05]i299: Plan complete, result: 0x0
    [0DE4:1D0C][2017-03-19T17:49:05]i000: Setting string variable 'IIF_MSI_SWITCHES' to value ''
    [0DE4:1D0C][2017-03-19T17:49:05]i000: ** MBA ** Getting window handle.
    [0DE4:1D0C][2017-03-19T17:49:05]i000: ** MBA ** Calling Engine.Apply(). Window handle: 788454
    [0DE4:24C4][2017-03-19T17:49:05]i300: Apply begin
    [1D38:121C][2017-03-19T17:49:09]i000: Caching bundle from: 'C:\Users\germa\AppData\Local\Temp\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\.be\SetupChipset.exe' to: 'C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\SetupChipset.exe'
    [1D38:121C][2017-03-19T17:49:09]i320: Registering bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, version: 10.1.1.14
    [1D38:0188][2017-03-19T17:49:09]i305: Verified acquired payload: SetupChipsetx64.msi at path: C:\ProgramData\Package Cache\.unverified\SetupChipsetx64.msi, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi.
    [1D38:0188][2017-03-19T17:49:09]i305: Verified acquired payload: cab4FADBDD6DC6637E75E196F741A3F14D1 at path: C:\ProgramData\Package Cache\.unverified\cab4FADBDD6DC6637E75E196F741A3F14D1, moving to: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\media1.cab.
    [1D38:121C][2017-03-19T17:49:09]i323: Registering package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, version: 10.1.1.14, package: SetupChipsetx64.msi
    [1D38:121C][2017-03-19T17:49:09]i301: Applying execute package: SetupChipsetx64.msi, action: Install, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'
    [1D38:121C][2017-03-19T17:49:28]e000: Error 0x80070643: Failed to install MSI package.
    [1D38:121C][2017-03-19T17:49:28]e000: Error 0x80070643: Failed to execute MSI package.
    [0DE4:24C4][2017-03-19T17:49:28]e000: Error 0x80070643: Failed to configure per-machine MSI package.
    [0DE4:24C4][2017-03-19T17:49:28]i319: Applied execute package: SetupChipsetx64.msi, result: 0x80070643, restart: None
    [0DE4:24C4][2017-03-19T17:49:28]e000: Error 0x80070643: Failed to execute MSI package.
    [1D38:121C][2017-03-19T17:49:28]i301: Applying rollback package: SetupChipsetx64.msi, action: Uninstall, path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\SetupChipsetx64.msi, arguments: ' MSIFASTINSTALL="7" IIF_MSI_SWITCHES="" ARPSYSTEMCOMPONENT="1"'
    [1D38:121C][2017-03-19T17:49:31]e000: Error 0x80070643: Failed to uninstall MSI package.
    [1D38:121C][2017-03-19T17:49:31]e000: Error 0x80070643: Failed to execute MSI package.
    [0DE4:24C4][2017-03-19T17:49:31]e000: Error 0x80070643: Failed to configure per-machine MSI package.
    [0DE4:24C4][2017-03-19T17:49:31]i319: Applied rollback package: SetupChipsetx64.msi, result: 0x80070643, restart: None
    [1D38:121C][2017-03-19T17:49:31]i329: Removed package dependency provider: {FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}, package: SetupChipsetx64.msi
    [1D38:121C][2017-03-19T17:49:31]i351: Removing cached package: SetupChipsetx64.msi, from path: C:\ProgramData\Package Cache\{FEBB7B48-CC1C-4A50-A497-FA21413F6BE9}v10.1.1.14\
    [1D38:121C][2017-03-19T17:49:31]i329: Removed package dependency provider: {23312E5E-F714-4F0B-97F5-4A7E2DEFE61E}, package: SetupChipsetx86.msi
    [1D38:121C][2017-03-19T17:49:31]i330: Removed bundle dependency provider: {619e726e-d2b4-4e28-9568-c964fd81ee6c}
    [1D38:121C][2017-03-19T17:49:31]i352: Removing cached bundle: {619e726e-d2b4-4e28-9568-c964fd81ee6c}, from path: C:\ProgramData\Package Cache\{619e726e-d2b4-4e28-9568-c964fd81ee6c}\
    [0DE4:24C4][2017-03-19T17:49:31]i000: ** MBA ** Apply complete. Status: '-2147023293' Restart: 'None' Result: 'None'
    [0DE4:24C4][2017-03-19T17:49:31]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart:  No
    [0DE4:1D0C][2017-03-19T17:49:31]e000: ** MBA ** Unknown error.

  • JackE
    JackE ACE Posts: 45,178 Trailblazer

    Then either try to install it again or, better yet,  let Win10 try to automatically update the driver thru Device Manager as described in my immediately preceding post. Jack E/NJ 

    Jack E/NJ