Recent Windows Update causing sizing issues

[DonKitchen]

ADMIN UPDATE

This is a regression issue in IE: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11295665/. 

Cast your vote by pressing the "+Me Too" button and encourage your end users to do the same if they have an account with Microsoft.

The problem with the RadWindow appearance will be fixed when Microsoft roll out a fix.

Cumulative updates through Windows Update should resolve the issue. First reported updates:

• Windows 10: https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217.
• Windows 7, Windows Server 2008: https://support.microsoft.com/en-us/help/4015549/windows-7-windows-server-2008-r2-sp1-update-kb4015549.

Fault condition description:

• IE is in some form of compatibility mode (IE8, IE9 or IE10), usually via an  meta tag. The issue does not manifest in standards (Edge) mode. Add a meta tag to enforce it.
• RadWindow is in Classic RenderMode. It uses tables to render. Using the Lightweight RenderMode should alleviate the problem.
• The end user machine has the KB4012204 update installed. Other updates that have been reported as associated with this issue: MS17-006, KB4012215, KB2952664, KB3216755, KB4013429, KB3218362. 

END UPDATE

The recent Microsoft Windows Update seems to be causing issues for us with our .

https://support.microsoft.com/en-us/help/4012204/ms17-006-security-update-for-internet-explorer-march-14-2017

Attached is an example of what's happening since this update was pushed down.

Any suggestions on a quick fix?

Clients are IE 11 using Compatibility mode (v8).

 

 

[DonKitchen]

Seems to happen regardless of compatibility mode or not in IE 11, FYI.

[Chris]

We've been trying to deal with this same issue most of the day too. A coworker has put in a support ticket but no response yet. In my case it's not causing the issue running in IIS locally but it is on the web servers. We also have one site out of 20 that's working fine and has exactly the same code except a few cosmetic things as a site that's having the problem.

[DonKitchen]

Well, not that I'm happy you're having issues but I am glad to know I'm not alone.  I will put in a support ticket also, which may help up the priority on this!

[DonKitchen]

Is yours IE 11 only also?  What else can you tell me about your user's experiencing the issue so that we can draw some similarities here?

[DonKitchen]

[quote]Chris said:We've been trying to deal with this same issue most of the day too. A coworker has put in a support ticket but no response yet. In my case it's not causing the issue running in IIS locally but it is on the web servers. We also have one site out of 20 that's working fine and has exactly the same code except a few cosmetic things as a site that's having the problem.[/quote]

Not that you want to go and change all your code (like I don't), but we've discovered that by changing the window to render in "Lightweight" mode it seems to fix the issue, or at least it's a workaround.

Attached is a sample of what I mean.

 

 

[Chris]

I can only verify IE11 for sure. Thanks for letting me know that. I can test out changing that in our skin file and hopefully only change it in one place.

[DonKitchen]

Good call on the skin.  We didn't have one for the Radwindow but I added one with just that property and it seems to do the trick.  It's out in our TEST environments now pending release.

[Nick]

Does anyone know what update is causing this?  My application is running an older version of telerik and I can't get it to run in lightweight mode.

[Chris]

It think it was https://support.microsoft.com/en-us/help/4013429/windows-10-update-kb4013429 for me. I installed 13 updates this morning and it looked the most likely to cause it.

This appears to be the the one if you're still on Windows 7: https://support.microsoft.com/en-us/help/4012204/ms17-006-security-update-for-internet-explorer-march-14-2017

[Chris]

Even with the lightweight rendering fixing it for most people we're still having one customer using IE 11.0.9600.18617 on Windows 7 have the same problem on 3 of his computers even after running IE in safe mode and resetting. Other people with the same configurations work fine.

This windows update is causing a lot of issues including breaking Microsoft Dynamics: http://www.infoworld.com/article/3181497/microsoft-windows/confirmed-windows-10-update-kb-4013429-breaks-microsoft-dynamics-crm-2011.html

[Nick]

On windows 7 using IE 11.0.9600.18537 it looks like it's actually kb412204, or a combination of the two anyway.  

[Marin Bratanov]

Hi guys,

I am pinning this thread to the top of the forum so everyone can easily monitor the progress of this issue.

We are currently investigating (thank you for submitting the tickets). We will get back to you there and we will also post information here as soon as we have it.

Regards,

Marin Bratanov
Telerik by Progress

[Richard]

Thanks for the update. One of our internal users noticed this issue the other day, but we were thinking it was just his computer as nobody else internally was having the problem. Then our customers started reporting it, and today one of our biggest customers must have gotten the update rolled out to all of their users and has been getting reports all morning.

This is a pretty huge issue for us, hopefully you can find a fix to the problem quickly. I just think it's crazy that a security update can affect something so basic and seemingly unrelated as content height within a window!

[Marin Bratanov]

Hi all,

I have just updated the first post with information on the matter.

Put shortly, this is a regression in IE and we must wait for a fix from Microsoft.

/*Updated 

This is a regression issue in IE: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11295665/. 

Cast your vote by pressing the "+Me Too" button and encourage your end users to do the same if they have an account with Microsoft.

The problem with the RadWindow appearance will be fixed when Microsoft roll out a fix.

Fault condition description:

• IE is in some form of compatibility mode (IE8, IE9 or IE10), usually via an  meta tag. The issue does not manifest in standards (Edge) mode. Add a meta tag to enforce it.
• RadWindow is in Classic RenderMode. It uses tables to render. Using the Lightweight RenderMode should alleviate the problem.
• The end user machine has the KB4012204 update installed. Other updates that have been reported as associated with this issue: MS17-006, KB4012215, KB2952664, KB3216755, KB4013429, KB3218362. 

Updated*/ 

Regards,

Marin Bratanov
Telerik by Progress

[Chris]

Can you try adding this to your site's css file without the lightweight rendering and let me know if it works for you? It seems to help for us but it's not fully tested yet:

        .RadWindow div.rwExternalContent iframe {
            height: 100% !important;
        }

[Marin Bratanov]

Hi Chris,

This does not help for me. I would not expect it to, because RadWindow already has such a rule (without the !important modifier, though).

The problem is in the IE rendering engine - IE8-10 modes have it. You should either add an X-UA Compatible meta tag with value IE=edge, or use the Lightweight mode. That is, until Microsoft roll out a fix.

Regards,

Marin Bratanov
Telerik by Progress

[Chris]

I was just curious and looking at the differences between classic and lightweight rendering modes with the IE DOM inspector and noticed the iframe on both of them had the height set to 100% with an inline style but on the lightweight mode the inline style was overridden by a style from the WebResource.axd that's just what I posted above. I thought the rendering engine might be picking that up and just have a bug with recognizing the inline style on the iframe. It actually seemed to help on one site but not consistently on others. At the moment I can't look at it any more today since lightweight rendering mode is working well enough for us.

[DonKitchen]

The problem I've seen is that if you are less than Edge the Lightweight won't work.  It falls back to classic.

And when we go to IE=Edge other things in our application aren't working or displaying properly!

[Marin Bratanov]

Hi guys,

@Chris - the key difference is the table the Classic mode uses. The IE bug is that the iframe in a table can no longer be 100%. Actually, not just iframes, but that's the relevant bit for us. Full details are available at the first post that I ammended.

@Don - as of R1 2017, the Lightweight mode can be configured to not fall back to classic in compatibility modes if the X-UA header is present: http://docs.telerik.com/devtools/aspnet-ajax/controls/render-modes#lightweight-rendermode. This mode targets modern browsers, so edge mode for IE is expected.

Regards,

Marin Bratanov
Telerik by Progress

[DonKitchen]

Right but X-UA header tag with IE=Edge changes you from 8-10.  We were already using that tag but had IE=8.

IE=edge causes us display issues in other areas of our system unfortunately.

Does that make sense now?

Rendermode cannot work unless IE=Edge, right?

[Trevor]

A workaround might be to use absolute positioning on the .rwWindowContent css class.

I took off the "height: 100% !important", and replaced it with "position: absolute; top: 38px; right: 15px; bottom: 15px; left: 15px". You might need to adjust the positioning slightly based on the RadWindow skin.

It's not perfect, but it might suffice until the permanent fix is available.

[Marin Bratanov]

Hi guys,

@Don - it is possible that this header is added from several places in the app and the IE8 mode takes precedences (e.g., if added via an HTTP header rather than as a meta tag). I understand your point about the edge mode causing issues with other places of the app, yet as a general rule of thumb I would recommend using this mode whenever possible with regard to our controls. The Lightweight RenderMode may work in compatibility modes such as IE9 and IE10 but there still may be some issues.

@Trevor - such an approach could work, but I would still recommend the Lightweight mode and/or the Edge mode of IE.

Regards,

Marin Bratanov
Telerik by Progress

[Harikrishnan]

Hi All,

     

[Harikrishnan]

Hi All,

I do have the same problem and tried with the above different solutions. But its not working.

Is there any update from Microsoft. 

Please help us. Client has started ....$#$###$##$%$%$%$%$

[ana]

Thank you Trevor. In my case I had to add table.rwTable to your suggestion and IE 11 is finally working!
I added the following to the master page:
    .rwWindowContent {
            position:absolute;
            top: 10px;
            right: 5px;
            bottom: 5px;
            left: 5px
        }
           table.rwTable{
           height:350px !important;
        } 
We are using an old version of Telerik controls (2011.2.712.40).

[Charlie]

Here's something that worked for me and wasn't too painful.  

In the .aspx that's opened by the RadWindow, I have this:

        $(document).ready(function () {

            parent.resizeRadWindow("RadWindow1");
        });

* "RadWindow1" is the name of my RadWindow -- sorry, not too creative on that one.

In my parent page (that opens the RadWindow), I have this:

            function resizeRadWindow(windowName) {
                $('[name="' + windowName + '"]').css({'height':($(".rwTable").height()+'px')})
            }

All my parent pages have the same master page, so I only have this in one place.  Yes, you have to add JavaScript to basically every RadWindow, which may not be practical for everyone.  Also, I have only tested this with RadWindows that are opened client-side.

[Harikrishnan]

Its worked . NO TIME TO WAIT FOR MICROSOFT :)

<asp:HyperLink ID="lnkSelect" runat="server" CssClass="PageHeadlinePortal" Style="font-size: 11px"
                                    EnableViewState="False" Text="Select Member" NavigateUrl="javascript:ShowDialogFromLink();"
                                    Visible="true"></asp:HyperLink>

function ShowDialog() {
             document.getElementById('hidMenuIdLink').value = "1";
        var oRadWindowManager = $find("<%= RadWindow.ClientID %>")
        var oWnd = oRadWindowManager.open(null, "UserListDialog");
    }

 <asp:ScriptManager ID="ScriptManager1" runat="server">
                    </asp:ScriptManager>
                    <telerik:RadWindowManager ID="RadWindow" RenderMode="Lightweight" runat="server" Overlay="false" ReloadOnShow="true"
                        Behavior="Close, Move" Modal="True" VisibleStatusbar="false" Skin="Black">
                        <Windows>
                            <telerik:RadWindow  ID="UserListDialog" runat="server" Width="550px" Height="580px"
                                Title="User List Dialog" NavigateUrl="~/selectionlist.aspx" />
                        </Windows>
                    </telerik:RadWindowManager>

 

 

 

 

 

css

iframe[name='UserListDialog']

{
min-height: 520px !important;
}

 

 

[Tim Black]

We just completed a Microsoft patch cycle and users are reporting issues.  So far, they all seem to relate to the <iframe> object rendered for a RadWindow.  Specifically, the height attribute rendered is set to 100% it no longer fills the parent container.  It must be set to a literal height "200px".

[Tim Black]

Also meant to include that the issue doesn't occur with Chrome or FireFox.

[DonKitchen]

I *almost* have mine fixed.  I'm trying not to specify any hardcoded heights as we have many Radwindows in our application, all with different heights.

The solution I'm working on is a CSS change in our site's main stylesheet.  I've got this so far and it's ALMOST working.  The issue I'm having is that for RadWindows that have long content that requires scrolling, the bottom is getting cut off, most likely by the same amount I'm specifying for the top margin.

Does anybody have any suggestions on how I can fix this?

Here's the style I'm using, and attached are two screen shots showing a situation where it's working, and one where it's not.

/* RadWindow fix */
.RadWindow {
    overflow-y: hidden;
}
.rwWindowContent {
    position: absolute;
    top: 30px;
    right: 7px;
    left: 7px;
    z-index: -1;
}

[Tim Black]

OK, a single CSS entry allows me to override the value.  However, I need a way to dynamically set that value to a percentage of the parent value.

.RadWindow td.rwExternalContent iframe {
height: 600px !important;
}

The value I need to reference would be the height value for .RadWindow table.rwTable

For instance, when it renders the height value of .RadWindow table.rwTable is equal to 600px and the height value of .RadWindow td.rwExternalContent iframe is equal to 100%.  Through manual testing, setting it to the height of rwTable or a little less works great.

I know I could do this via JavaScript, but do any of you CSS gurus know if there is a way in CSS to reference a value from another CSS element?

 

[DonKitchen]

[quote]DonKitchen said:

I *almost* have mine fixed.  I'm trying not to specify any hardcoded heights as we have many Radwindows in our application, all with different heights.

The solution I'm working on is a CSS change in our site's main stylesheet.  I've got this so far and it's ALMOST working.  The issue I'm having is that for RadWindows that have long content that requires scrolling, the bottom is getting cut off, most likely by the same amount I'm specifying for the top margin.

Does anybody have any suggestions on how I can fix this?

Here's the style I'm using, and attached are two screen shots showing a situation where it's working, and one where it's not.

/* RadWindow fix */
.RadWindow {
    overflow-y: hidden;
}
.rwWindowContent {
    position: absolute;
    top: 30px;
    right: 7px;
    left: 7px;
    z-index: -1;
}

[/quote]

Nevermind, the overflow-y makes the popup NOT scroll in Chrome.

[Tim Black]

For a JavaScript approach, Charlie's solution works just fine.  However, I use a lot of RadWindows throughout the site, so this would require repeating this code in numerous pages.

[Marin Bratanov]

Hi guys,

@Don - if you specify top, bottom, left and right for the absolutely positioned iframe, you should be able to get the proper scrollbars, as Trevor suggested above.

@Tim - doing this with JS is going to be quite cumbersome, as you will need to take into account resizing of the RadWindow as well. This includes maximizing too. The CSS approach Trevor offered is so far the cleanest workaround.

Regards,

Marin Bratanov
Telerik by Progress

[Brijesh]

Hi All,

RenderMode="Lightweight" solves the pop-up size concern. However, I cannot see the top border anymore and i cannot click on close button because of that.

I changed the the Document mode to IE 11 and kinda worked for me at least for pop-up.

<meta http-equiv="X-UA-Compatible" content="IE=11" />

I am still checking if it affects anything else or not before moving this to production.

Also, below Microsoft updates of 22 March says that this issue has been resolved. I am checking that as well.

https://support.microsoft.com/en-us/help/4016635/windows-10-update-kb4016635

Thanks

 

[Chris]

Make sure you change the RenderMode on both the RadWindowManager and the RadWindow.

[DonKitchen]

Good news, Microsoft has released a patch that (so far) seems to resolve the issue.

Bug report link: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11295665/

Text and download links for the fixes, from the above URL:

The fixes have been released and are public available the catalog:
Windows 10 Version 1607:
KB-article: https://support.microsoft.com/en-us/help/4016635
Package-location: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4016635
Windows 10 RTM Version 1507
KB https://support.microsoft.com/en-us/help/4016637
Package http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4016637
IE11 on Windows 7 and Windows 8.1
KB https://support.microsoft.com/en-us/help/4016446/
Packages: http://www.catalog.update.microsoft.com/search.aspx?q=kb4016446
Please keep in mind, that the packages for Windows 10 are full cumulative Updates and do not have Prerequisite for their installation.
The packages for Windows 7 and Windows 8.1 are different, as they 1 just contain the DLL from the rendering-engine and needs to be installed on top of the March IE-Update KB4013073 for Internet Explorer.

[Tim Black]

I removed my workaround code in one page and verified the issue returned.  I then installed the Microsoft fix and verified it does fix the problem.

[ana]

Tim, can you tell me the number of the Microsoft fix you installed? there are several.

Thank you

[Tim Black]

4016446

[JARROD R]

[quote]DonKitchen said:

Good news, Microsoft has released a patch that (so far) seems to resolve the issue.

Bug report link: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11295665/

Text and download links for the fixes, from the above URL:

The fixes have been released and are public available the catalog:
Windows 10 Version 1607:
KB-article: https://support.microsoft.com/en-us/help/4016635
Package-location: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4016635
Windows 10 RTM Version 1507
KB https://support.microsoft.com/en-us/help/4016637
Package http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4016637
IE11 on Windows 7 and Windows 8.1
KB https://support.microsoft.com/en-us/help/4016446/
Packages: http://www.catalog.update.microsoft.com/search.aspx?q=kb4016446
Please keep in mind, that the packages for Windows 10 are full cumulative Updates and do not have Prerequisite for their installation.
The packages for Windows 7 and Windows 8.1 are different, as they 1 just contain the DLL from the rendering-engine and needs to be installed on top of the March IE-Update KB4013073 for Internet Explorer.

[/quote]

@DonKitchen - do you know if this will be released with the automatic windows updates, or will users have to update manually?  

[DonKitchen]

[quote]JARROD R said:

@DonKitchen - do you know if this will be released with the automatic windows updates, or will users have to update manually?  

[/quote]

I do not.  I do know that some of the links were down for a bit.  Not sure if all is good now or if they will roll them up into Windows Updates.  Please share if you find anything!

[Edward]

Will this be a fix by Microsoft or Telerik?  I'm just not getting this to work since the 15th when the updates happened.  If you put it in Edge mode - then the dirty flag is being set to true even though nothing has changed.

[Marin Bratanov]

Hi Edward,

We intend to let the official patches from Microsoft propagate, as they are the true fix for the problem.

If reports indicate they do not resolve the issue or they do not disseminate well enough, we will consider implementing a fix in our codebase.

Regards,

Marin Bratanov
Telerik by Progress

[Donald McLean]

I have two issues which seem to be inter-relelated. I have the issue of the Report viewer being scrunged up and also the fact that the print button in the report viewer seems to not work.

Originally I had <meta http-equiv="X-UA-Compatible" content="IE=8" /> this on each page of my application. I was informed that in IE 11 for Windows 10 that reports were all squished, however, in IE 11 for windows 7 it was not squished. Also, I have the report viewer opening up in regular window instead of a rad window so that are clients could work on a report have it on one screen and make changes to the data on another screen then refresh the report to see the updated report.  So, I removed the tag from the pages and the pages magically were unsquished itself.

Then, I was informed that the print button no longer worked. So, I started experimenting and found that if i used <meta http-equiv="X-UA-Compatible" content="IE=8" /> or changed content to 9 or 10 the print button worked, however the report was squished, however if I remove it or change the content to be IE=edge,chrome=1 then the report is unsquished but the print button doesn't work. By the way when I say the print button doesn't work, I mean it automatically wants to export to a pdf instead of bringing up the print dialog.

I have been working on this for the last several days and I am not making much progress so I thought I would reply to this post that one of my coworkers found yesterday. Any and all help would be greatly appreciated.

[Katia]

Hello Donald,

By default, reports are printed using the PDF plug-in of the browser. When the plug-in is not available or not supported, the widget falls back to exporting to a PDF file.
The printing behavior can be controlled manually through the printMode option. More detailed information about HTML5 Report Viewer's printing behavior can be found in Printing Reports help article.

As this question is not directly related to the main subject of the current forum thread, please open a new thread in Telerik Reporting forum in case you need any additional clarifications.
 

Regards,
Katia
Telerik by Progress

[JARROD R]

[quote]Marin Bratanov said:

We intend to let the official patches from Microsoft propagate, as they are the true fix for the problem.[/quote]

Marin,  Do these updates still have to be manually installed or have they been released to a automatic windows update?

[JARROD R]

Sorry to reopen all of this, but here is my issue.  We use a ton of RAD windows in our application and I am pretty sure we aren't doing anything out of the ordinary.  Therefore, it seems that what I am reading from a Telerik employee is that since Microsoft broke it, they either have to fix it or we have to try to use some work around

For the work around, I don't see one that Telerik provided as an official fix.  Just some people saying on the forum that they've tried some things out that "seem" to work.  If I have missed this fix from Telerik, or one that will definitely fix it, then my apologies and I'd appreciate someone pointing it out to me.

For the Microsoft fix, I now have to contact all my customers and ask them to manually install this fix from one of the links provided.  This is very unreasonable.  

1.  Many will have to get their IT involved, since they don't have the rights to install stuff on their computers.  I've already had this happen with one.  I imagine they won't be the only one.  

2.  Has anyone looked at those links?  If I gave one of those links to the average computer user, with all the choices to install, they would have no idea what to choose.  Therefore I am going to have to walk each one through it.  

I understand how Telerik must feel about Microsoft releasing updates that break their stuff.  Is anyone from Telerik talking to Microsoft about this, to see if they are going to roll it back or package this in an official update?

Could anyone else offer any suggestions on how they are handling it with a large amount of users that might need this update?

Thanks for all comments.

 

[Tim Black]

Hi Jarrod,

Though I had a lot of code that was affected by this issue, I was lucky since mine was all internal to our facility.  I quickly jumped in, reviewed what was posted and found Charlie's suggestion resolved my issue.  However, Microsoft issued a fix much faster than I expected, so I ended up backing it out later after I verified their fix worked.

**** CHARLIE'S SUGGESTION ****

In the .aspx that's opened by the RadWindow, I have this:
        $(document).ready(function () {
            parent.resizeRadWindow("RadWindow1");
        });
* "RadWindow1" is the name of my RadWindow -- sorry, not too creative on that one.
In my parent page (that opens the RadWindow), I have this:
            function resizeRadWindow(windowName) {
                $('[name="' + windowName + '"]').css({'height':($(".rwTable").height()+'px')})
            }

 

[Marin Bratanov]

Hi guys,

@Jarrod - we did escalate the issue so it got fixed. To be honest, I assumed they will ship it in Windows Update. It seems that this has not happened yet, and I will look into this as well. Thanks for bringing it up.
As for workarounds - my edit in the initial post contains a couple (use the Lightweight RenderMode; move out of compatibility mode towards Standards/Edge mode, either via a meta tag, or by involving your local IT if you are in an Intranet). The other workarounds found by our clients are also valid options and I have marked them as answers to the thread. Personally, I like the position workaround from Trevor the most: http://www.telerik.com/forums/recent-windows-update-causing-sizing-issues#CAwInVR-1EiM-J8g-YDZVg.

@Tim - you may want to run that in the OnClientResizeEnd and OnClientCommand if it were Maximize or Restore.

Regards,

Marin Bratanov
Telerik by Progress

[JARROD R]

@Martin - Thanks for this reply, summarizing some of the suggested fixes.  I'll look into the ones you referenced.  This will help.  

Please do follow-up on this thread after you receive word from Microsoft regarding a packaged version of this update, that might be rolled out to customers a bit easier.  

@Tim - Thank you for your input and suggestion also.  

I appreciate both of you!

[Tim Black]

Since my RadWindows are dialog and do not display minimize\maximize\pin that is not an issue.  Thanks

[Thomas]

Hi all;

Yesterday (4/11/2017) Microsoft released the cumulative update KB4015217 for windows 10:

https://support.microsoft.com/en-us/help/4015217/windows-10-update-kb4015217

I don't know offhand whether one was released for windows 7 or other OS's.  I'm still trying to determine if this cumulative update includes the fix for sizing issue.  I'd installed the KB4016635 fix manually a couple weeks ago and am going to try to uninstall it and see if the radwindow issue comes back.

If anyone else knows or can definitively determine whether the KB4015217 update includes the fix for the sizing issue, please chime in.

Thanks!

[Thomas]

More info:  my "Installed Updates" screen no longer lists KB4016635 as installed on my my machine (I had uninstalled it yesterday before I knew about the cumulative update), it does list KB4015217, and I am *not* experiencing the sizing issue on RadWindows.

[Marin Bratanov]

Hi Thomas,

According to the KB article, the cumulative update KB4015217 that should come from Windows Update will contain a fix for this issue, as it supersedes KB4016635 (i.e., includes it and adds more fixes).

I am not sure of exact numbers for other OS versions, but such cumulative updates through Windows Update should arrive for them as well.

Regards,

Marin Bratanov
Telerik by Progress

[JARROD R]

A quick update.  As discovered by Thomas, the April updates seemed to have fixed this issue on his computer.

I have verify wanted to verify, so I tested on a computer that had not been updated.  I first installed the March update, which did indeed cause the issues in this thread. (KB4012215 for Windows 7)

I then installed the only the April update, which then fixed the issue.  (KB4015549 for Windows 7)

Therefore, if users just update their windows OS, this will be fixed automatically.  Thanks for all the input from @Marin and others.