Results 1 to 4 of 4

Thread: Asus isn't hosting adverts in its GPU Tweak II software

  1. #1
    HEXUS.admin
    Join Date
    Apr 2005
    Posts
    31,709
    Thanks
    0
    Thanked
    2,073 times in 719 posts

    Asus isn't hosting adverts in its GPU Tweak II software

    GPU 'ad' screen widely shared online shows simple placeholder for a streamer's logo option.
    Read more.

  2. #2
    Registered User
    Join Date
    Jan 2019
    Posts
    5
    Thanks
    0
    Thanked
    0 times in 0 posts

    Re: Asus isn't hosting adverts in its GPU Tweak II software

    If only I could update the damn thing and not have it fail due to my PC having a newer C++ redist...

  3. #3
    Registered User
    Join Date
    Dec 2017
    Posts
    9
    Thanks
    0
    Thanked
    0 times in 0 posts

    Re: Asus isn't hosting adverts in its GPU Tweak II software

    It fails not because you have newer VC++, but because you lack the matching runtime version - as they are targeted at compile time.
    Best to install all VC++ versions (2005,2008,20010,2012,2013,2015,2017..) avoid the hassle..

  4. #4
    I'm special azrael-'s Avatar
    Join Date
    Jan 2014
    Location
    Aarhus, Denmark
    Posts
    1,074
    Thanks
    67
    Thanked
    113 times in 92 posts
    • azrael-'s system
      • Motherboard:
      • ASUS Prime X470-Pro
      • CPU:
      • AMD Ryzen 7 3800X
      • Memory:
      • 64 GB ECC DDR4 2666 MHz (Samsung M391A2K43BB1-CTD)
      • Storage:
      • 1 TB Samsung 970 EVO Plus, 1 TB Samsung 850 EVO, 12 TB WD HDDs
      • Graphics card(s):
      • eVGA GTX 1080 SC Gaming, 8 GB
      • PSU:
      • Seasonic X-Series 560W
      • Case:
      • Corsair Obsidian 550D
      • Operating System:
      • Windows 10 Pro x64
      • Monitor(s):
      • Acer Predator XB271HU
      • Internet:
      • VDSL 55/12 Mbit/s

    Re: Asus isn't hosting adverts in its GPU Tweak II software

    Quote Originally Posted by udisy View Post
    It fails not because you have newer VC++, but because you lack the matching runtime version - as they are targeted at compile time.
    Best to install all VC++ versions (2005,2008,20010,2012,2013,2015,2017..) avoid the hassle..
    Not entirely correct. In MSVC you can bind your code to use the specific build of the MSVC libraries you're currently developing with. Usually because your code is reliant on a particular feature or fix. You would then be expected to ship the necessary runtime redist version of the libraries with your product.

    For the end user it's usually enough to install one build of the respective MSVC runtime, and that would/should usually be the latest one available. You can't mix and match runtime libraries, however. An application built with MSVC 2008 can't use the MSVC 2012 runtime (and would be looking for different files anyway). With the possible exception of MSVC 2015 and 2017. That is because MSVC 2017 is binary compatible with MSVC 2015.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •