Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Bloomberg Terminal conflicts with Win10 Fall Creators Update

    Home Forums AskWoody blog Bloomberg Terminal conflicts with Win10 Fall Creators Update

    This topic contains 13 replies, has 8 voices, and was last updated by  Kirsty 1 week ago.

    • Author
      Posts
    • #144574 Reply

      woody
      Da Boss

      Bloomberg is advising that customers running Bloomberg Terminal need to refrain from upgrading to Win10 FCU, version 1709. Per their professional supp
      [See the full post at: Bloomberg Terminal conflicts with Win10 Fall Creators Update]

    • #144590 Reply

      Cybertooth
      AskWoody Lounger

      Microsoft continues its bull-in-a-china-shop routine, breaking things right and left as it stumbles along toward an uncertain future.

      The solution, as always, is for the world to adjust to Microsoft’s requirements, and not for Microsoft to keep its products compatible with the rest of the world.

      I am reminded of Bertolt Brecht:

      …the people had forfeited the confidence of the government and could win it back only by redoubled efforts. Would it not be easier in that case for the government to dissolve the people and elect another?

       

      1 user thanked author for this post.
      • #144684 Reply

        woody
        Da Boss

        Weil die Dinge sind, wie sie sind, werden die Dinge nicht so bleiben wie sie sind.

        2 users thanked author for this post.
    • #144637 Reply

      anonymous

      I had my moments with 1709 on Monday… Installed it and I even tried to like it. But this must be one of the worst Windows versions ever. Last time I was that disgusted was with Windows 8 and Vista on “Vista capable” hardware.

    • #144695 Reply

      MrJimPhelps
      AskWoody MVP

      What will happen if they aren’t able to fix whatever is causing this problem by the time that all Windows 10 users are required to move to 1709? Will that mean that a whole lot of people won’t be able to access Bloomberg Terminal?

      I’ll bet that same question could be asked about a lot of things that people access on a regular basis. A while back I worked at an oil company. The users who sold the oil that we found used an old software package to do so, because the site they logged into required it. Following this logic, at some point the oil company won’t be able to log on to sell their products unless the site updates their software requirements.

      • #144715 Reply

        johnf
        AskWoody Lounger

        What Windows 10 needs is the equivalent of what XP Mode was to Windows 7, so that older programs that didn’t run well in Win7 but ran fine in XP could continue to run until they were updated.

        Linux is approaching the problem in a different way (sandboxing apps using Flatpacks or Snaps, so it won’t matter which distro they run on as long as they support Flatpacks/Snaps).

        And yes, I know there are work arounds to get XP Mode on Win10, but there are licensing issues, etc., with that approach. A built in “Windows 7 Mode” for Windows 10 would solve a lot of issues!

         

        2 users thanked author for this post.
        • #144858 Reply

          AlexEiffel
          AskWoody Lounger

          Good idea, but maybe people would end up only using Win 7 mode, which is certainly not what Microsoft wants…

    • #144860 Reply

      MrJimPhelps
      AskWoody MVP

      What Windows 10 needs is the equivalent of what XP Mode was to Windows 7, so that older programs that didn’t run well in Win7 but ran fine in XP could continue to run until they were updated….And yes, I know there are work arounds to get XP Mode on Win10, but there are licensing issues, etc., with that approach. A built in “Windows 7 Mode” for Windows 10 would solve a lot of issues!

      That ability already exists in Windows 10, with Hyper-V. The only thing Hyper-V lacks that XP Mode provides is that you don’t get the free OS with Hyper-V like you do with XP Mode.

      So if you have a retail license for Windows 7, you could run it in a Hyper-V session in Windows 10 right now. Same thing for Linux, XP, whatever OS you want.

      • #144957 Reply

        anonymous

        True about Hyper-V, but then the user would have to do a full install of the OS. The advantage of a “Windows 7” mode is that all the work would be already done for them. Having to do full installs is a big part of why Linux isn’t as popular on the desktop, since most users don’t install Windows to get their systems going.

        I’m not familiar with Hyper-V, so I don’t know if you can set it up like XP mode (for example, setting up an icon on your desktop that would run the XP program without having to sign into a virtual environment).

        “Windows 7” mode would make it much easier for the average user to dump Windows 7, since they can still run apps that don’t have newer versions, or use older equipment (like printers, etc) that are still functional.

        If MS is giving Win10 away for free, I’m not sure why they would object to giving people a secondary free license to run Win7 in a VM, other than trying to push software in their app store.

        • #145124 Reply

          MrJimPhelps
          AskWoody MVP

          I doubt they will ever provide a “Windows 7 Mode”, because Microsoft’s attitude toward the customer has changed. They are moving away from the old model of doing their very best to meet the customer’s needs. They are now moving to the new model of Windows as a Service, in which they do their best to force everyone to do things the Microsoft way.

          But I agree, it would be nice.

          XP Mode for Windows 7 was one of the most customer-friendly things Microsoft has ever done. It was the sort of thing that engendered a whole lot of loyalty to Microsoft.

          1 user thanked author for this post.
    • #145123 Reply

      MrBrian
      AskWoody MVP

      From Windows 10 Fall Creators Update causes issues when it calls CreateWindowEx in some 32-bit applications (my bolding): “In some cases, the Windows 10 Fall Creators Update (Version 1709, build 16299.19 or 16299.15) causes crashes or other issues when it calls the CreateWindowEx function in some 32-bit applications. We are aware of issues that affect some Microsoft Visual Studio extensions and Bloomberg Professional services.”

      • This reply was modified 1 week, 1 day ago by  MrBrian.
      • #145133 Reply

        MrBrian
        AskWoody MVP

        From Defer installation of the Fall Creators Update to avoid crashes in Visual Studio (my bolding):

        “The Windows 10 Fall Creators Update (FCU) 1709 contains a bug that causes CreateWindow() and CreateWindowEx() to fail unpredictably. The bug prevents Visual Assist from rendering all components of its UI, and eventually causes Visual Studio to crash.

        Microsoft has acknowledged the CreateWindow() bug and is investigating its cause, but the bug will not be fixed—at the earliest—until the December Patch Tuesday. If you want to use Visual Assist until Microsoft releases a fix, defer installation of the Windows 10 Fall Creators Update.

        Separately, Microsoft broke Windows hook procedures in Windows 10 Build 15063.608, issued Sept 12th. The hook bug causes Visual Studio to crash intermittently, e.g. when opening certain dialogs of Visual Assist. Microsoft has acknowledged the bug and is scheduled to release a fix on November Patch Tuesday.

        • This reply was modified 1 week, 1 day ago by  MrBrian.
        • This reply was modified 1 week, 1 day ago by  MrBrian.
        1 user thanked author for this post.
      • #145145 Reply

        woody
        Da Boss

        So that’s what’s happening….

    • #145154 Reply

      Kirsty
      AskWoody MVP

      Windows 10 Fall Creators Update causes issues when it calls CreateWindowEx in some 32-bit applications
      Article ID: 4054150 – Last Review: 11 Nov 2017 – Revision: 15
      Applies to: Windows 10 version 1709

      Workaround:
      To work around this issue, roll back your Windows 10 installation to the previous version of Windows.

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Bloomberg Terminal conflicts with Win10 Fall Creators Update

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information:


    Comments are closed.