.Net Framework 4.6.1 & Folder Redirection issue

[Chuckster]

Security Update for Microsoft .NET Framework 4.6.1 on Windows 7 (KB3122661)

Security Update for Microsoft .NET Framework 4.6.1 on Windows 7 (KB3127233)

Microsoft .NET Framework 4.6.1 for Windows 7 (KB3102433)

 

These three updates break folder redirection. It's on every workstation but it's hit and miss. On some workstations people are able to get their redirected folders, e.g. home drive, favourites etc, and on other workstations they can't.

 

In the Event Viewer it logs it down with an event id 502.

 

Uninstalling the 3 updates cures my problem.

 

Anybody else experience this since Tuesday's updates were released from MS?

[Michael]

Interesting, thanks for the heads up. My immediate thoughts are what has a .NET Framework update got to do with Folder Redirection?

 

I wonder if Windows 8, 8.1 and 10 have the same issue?

[Chuckster]

My school is entirely Windows 7, so I can't comment on the other OSes. However, I do have it installed on all the 2012 R2 servers.

 

I was surprised by the .NET Framework, as I was simply uninstalling the most recent updates. Took .NET Framework off and my problem was cured. All other updates from Tuesday remained.

[Michael]

I guess in the short term, do you actually need .NET 4.6.1 or just .NET 4.6 or even an earlier build? Windows 10 for example has .NET 4.6 as standard and I have this version installed on all servers too... primarily for security reasons. I haven't looked at .NET 4.6.1 as there's no requirement as yet.

[googlemad]

We have been informed by Capita that 4.6.1 will be required for the upcoming release of our UNIT-e MIS system (Basically the FE version of SIMS.net). Glad I haven't already started applying the update if this is the case!

[tech-man]

Does anyone have anymore feedback on this?

[gshaw]

Was wondering if to approve 4.6.1 when it appeared on WSUS, glad I haven't yet if this thread is anything to go by!

[pleach85]

It's also not supported on exchange servers at the moment, just in case anyone with an in house exchange server is thinking of rolling it out.

On .NET Framework 4.6.1 and Exchange compatibility - Exchange Team Blog - Site Home - TechNet Blogs

[Arthur]

The .NET Framework 4.6.1 (KB3102467) also causes the RD Gateway Management Console to crash.

 

https://blog.workinghardinit.work/2016/02/15/rd-gateway-management-console-crashes-with-net-framework-4-6-1-update-kb3102467

 

Apparently the Exchange console and Skype for Business Server 2015 is not the only victim of Microsoft pushing out the .NET Framework 4.6.1 update (KB3102467) to servers via Windows updates and WSUS. A colleague of mine described Windows updates as a game of Russian roulette, indicating there’s at least a QA concern.

 

The most recent victim I found was the RD Gateway management console on Windows Server 2012 R2. You might have the same issue on older Windows Versions but I’m only running W2K12R2 (it’s 2016 after all).

 

The result is that when you’re editing a Connection Authorization Policies or Resource Authorization Policies their membership settings (adding/removing groups) the MMC just crashes. Creating new ones is equally problematic!

[psydii]

dotnet update (and those for powershell, which builds on the framework) on servers have always needed special attention. Always read the release notes... and never be first to jump to install a non-security update in a production environment.

 

Though in the OPs case I'm not sure what components could possibly have an impact on the network/shell as they are part of the classic NT driver/api stack in Windows 7. Perhaps there is a third party app running with a dependancy on .net that gets hooks deep into the Windows, and it is this that is broken by the update, with folder redirection being collateral damage? (I'm thinking something like impero/netsupport etc).

[Michael]

Well until Microsoft fix this mess, .NET 4.6.1 isn't being installed or deployed. Just not worth the hassle so it seems right now. I'd advise everyone else to hold back too.

[gshaw]

Had a funny feeling a thread like this would pop up after seeing a new version of .NET appear, Microsoft haven't disappointed... the sloppy quality updates continue

[snagrat]

Apart from the OP has anyone had this issue as I haven't

[free780]

Must have made all the testers redundant.

[Chuckster]

Also worth bearing in mind that not only did it mess up folder redirection, but it also screwed up DFS. I have had to recreate the share names with different share name from the original, which got it going again. If you delete the shared name and recreate it with the original shared name it doesn't work.

[PyROm]

Doing the regfix in this thread fixed it for us http://www.edugeek.net/forums/windows/123347-failed-apply-folder-redirection-desktop-start-menus-suddenly.html

[Chuckster]

I have that regfix as a startup script and that issue is caused by some other update that was released a few years back. What the new .NET Framework update has done is cause an issue that by my own experiences can't be fixed unless you either uninstall the update or recreate your shares.

 

Uninstalling the update does not fix the issue, as he issue will forever remain until you fix it. If you haven't approved the update in WSUS, then you're fine and you won't experience the problem until you do install it.

[Michael]

Will be interesting to see if Microsoft release a .NET Framework 4.6.2 or release a fix for .NET Framework 4.6.1... but still how can we possibly install this moving forward if it breaks functionality elsewhere?

 

As I say, I'm happy with .NET 4.6.0 for now, so no requirement to deploy .NET 4.6.1 at the current time.

[psydii]

They usually update the broken things to support the revised frameworks. Both windows and exchange have regular cumulative updates which I would expect bring comparability with 4.6.1 in due course.