Version 10 1803 download slow






















Books Video icon An illustration of two cells of a film strip. Video Audio icon An illustration of an audio speaker. Audio Software icon An illustration of a 3. Software Images icon An illustration of two photographs. Images Donate icon An illustration of a heart shape Donate Ellipses icon An illustration of text ellipses. Windows 10 Item Preview. EMBED for wordpress. Yes, the problem with disable RemoteFW will only be solved in some cases, but as well as in my case when a customer uses a touch-based HW application and a graphics application, that's a step back.

Please if someone comes up for a functional solution or write a patch update please write well thank you. We've just got reports from a handful of our clients who've updated to that they're experiencing the same problems. Looking forward to a response from Microsoft on this one. While I'm waiting I've also replaced the mstsc.

Since they are system files, you have to take ownership of the files before Window will allow you to copy over them. This utility helps automate that process a bit. For folks with more than a few systems to take care of, I'd wait for the hotfix from Microsoft, but if you only have a few this will help. No problem guys, we're on it. We also opened a case with MS. Steve J. Microsoft seems unable to do that. Did you get a new hotfix version today?

Glad you found it helpful. It works well. Remote app is also possible. Thursday, May 17, AM. Janto 0. There are no peripherals available in the store application. It is not possible to use printer and other peripheral devices, such as serial port mapping. Thursday, May 17, PM. We too are experiencing this issue with Disabling RemoteFX graphics helps but limits the app's other features. Eagerly awaiting fix. We are also affected, how can we add to the same ticket so they are aware of how far reaching this issue is?

You can add your feeds and keep using the remote app. Numb13 thanks for the recommendation but this isnt a workable solution in a business environment. What do you think we use it for. About 50users. All using remote app. Now because of the update we are all using the app from the store. Unfortunately that doesnt work when you require full device integration. We also have several thousand users that rely on this to function.

Hopefully Microsoft gets this figured out soon. Hey guys, An update for now: We heard back from MS, and they are now asking us to deploy a to test to make sure that the issue happens there. I would appreciate a confirmation. The recommended way to report this to MS apparently is to use the Feedback Hub. Be sure to select 'Problem'. Thanks guys. Hopefully if we all send in reports this will be bumped in priority. We are noticing the same issue under ax Please let me know if you find a better workaround.

We can verify this as well on Server Also submitted feedback via the Feedback hub, to support the cause :. Headed to feedback hub now, thanks guys for staying actives, nice to have a community behind this. Same here. Friday, May 18, AM. Have reported on the feedback hub also. Look forward to any updates Very surprised and let down that this has taken so long to fix.

Friday, May 18, PM. Hope you guys don't start experiencing this as well. We are asking our clients to roll back the Windows updates using "Recovery Options" until Microsoft fixes this. EXE in the reason why apps are not working.

If they get enough people not installing or uninstalling the update due to an error that should prompt a more urgent response. Have had to roll back mstsc. That's an interesting, and crappy discovery! Thanks for the heads up on it! They do apologize for the "inconvenient" though :-D I think at this point, the best route is to hammer them with reports about the problem, and if you can even open a case with MS yourselves. We have to keep the pressure on.

I've made accounts on twitter, reddit, facebook, HN to try and get this more attention. Bit ridiculous I have to act like this to try and get information. I have Dynamics ax , Windows server R2. Remote Desktop App for the Dynamics. The same issue, I click in the botton and it is not display the information. What's going on????????? It's imperative that you fix all these bugs ASAP. Anyone have any good resources they use to keep on top of what's coming up with patches?

Pretty much same for me. I actually think Microsoft doesn't even know what they are putting out or what will make the cut until the last minute anyway. This is evident by their lack of quality control and in house testing. I was afraid of this answer. Still no news from Microsoft. I'm still asking affected users to make bug reports.

Let's keep it up, I really don't think Microsoft is concerned with this problem or has a full understanding just how many people are affected. Saturday, May 19, PM. Good monday everybody.

Have anybody found something new about this? Monday, May 21, AM. I was thinking over the weekend, another option might be if your router has the ability you could block the Microsoft update URL'S from the router side just to get past the 60 day limit before the operating system forces the update. That is of course, unless Microsoft gets off their rear and fixes this issue. Monday, May 21, PM. Hello, We have the same problem at our company. The Mac computers uses Microsoft Remote Desktop.

So I tried it on the W10 machines and with sucess. MS is being way slow in responding to this issue. Quite disappointing. I will monitor and update this thread ASAP. Thanks, Ron Stock Sr. Starting to get dire on our end. Only working solution for us has been reverting to and some users no longer have that option. Thank you Ron Stock! We're all eagerly waiting! Thanks for your work on this!

Tuesday, May 22, AM. Ron, thank you very much for the information. We're excited to hear this is being looked at. Dont worry about changing permissions before files swap. Should not have updated our users to This issue is even worse than the old Z-index problem. Now we cant use our CRM system at all.

Other than context-menu issue, anyone noticed the taskbar windows-preview not appearing as well for RemoteApps? I am hopeful nothing else breaks after fixing the newly identified issues. Thanks Ron for your attention to this issue, it's causing a lot of pain.

Tuesday, May 22, PM. Thanks for the post Fireballcz, that's good information, but you still have to change the permissions on the files before the operating system will allow you to overwrite them. You guys can use the script on the "Knowall IT" blog, which can take care of all the permissions. Can't vouch for the quality of the files downloaded, but you can always point them to your own source.. Yes, that is the issue I'm currently dealing with.

Just wondering I'm right there with ya. I feel like I have self control. I only check it about once an hour Refreshing every 20 min's. Two or three times a day for me. Wednesday, May 23, AM. My finger is on button. Hot Fix when you come and save me Same problems. Can you share please?? The only acceptable solution is a new windows update or a rollback of the previous update. Not everyone has access to all of their client's computers.

Wednesday, May 23, PM. I concur. Client computer tweaks etc. Besides lack of access to client computers, need for coordination with X number of users etc.

People're going to be pretty unhappy if the IT department keeps changing stuff on their computers all the time. And, it's a significant time sink as well, lots of users may not be too tech savvy and may require hand holding to walk through the patch, thereby consuming valuable time. Yes, I'm f5ing this thing every few minutes. Proposed as answer by M.

After logging out and signing in again, touching the remote app works Thanks. Edited by M. Janto Wednesday, May 23, PM. Hey Ron, we have this weird issue since updating to , but this only happens with Server "R1" as session host and not with all applications. We never had this issue with earlier Win10 Versions we rolled back to This is exactly what has been happening with our RemoteApp windows from Server "R1" with clients running Windows 10 Maybe you think it's acceptable to leave millions of clueless users in a state of not being able to run their businesses but pretty much the rest of the world does not feel the same.

This problem has been going on for quite some time and here we are, still waiting for a solution from Microsoft when the solution is right in front of your face, roll this trash update back and when you can get all the bugs worked out, force it on people again.

You're saying that Microsoft needs to rollback the entire update for their entire userbase to fix a problem that a small subset of their users who happen to usually be businesses are experiencing, or are you suggesting that they push out the MSTSC files as a new update, or perhaps just venting?

Not trying to get you riled up or anything. I'm just trying to understand what the suggestion you're offering entails. He just said it with a bit more zest!

This has been a quick and easy "temporary" fix. Thank you. Yep sadly noone seems to be still using r1 especially not with remoteapp so they probably won't fix that I'm afraid. I already posted a few threads and comments and tried to contact Microsoft but noone could help. Thank you This problem affects more than just Americans. Thursday, May 24, AM.

Note: I'm about to rant, so please feel free to skip if it's irrelevant! Ron Stock: I understand that you are not in control or a decision maker in what I'm about to state, so please don't take it personally, but, what I would expect, is that you do your best to escalate this concern to the powers that be at Microsoft to improve this process.

See anything one sided in this? This is from yesterday, and quoted by the MS Support Engineer, about 14 days after opening the ticket about the issue: Really? Here they are: 1- and that is ideal: Test Test and Test before releasing. Here's the response, verbatim: Seriously? Thanks for your time. Thursday, May 24, PM. Microsoft - please listen to your customers.

We will be rolling back many people. EXE in the box below to be consistent. Microsoft should just sent a hotfix of the previous version. Urgent problem solved. Then go back to the drawing board on the "new version". We've a few hundred RemoteApp customers across 4 continents and this is burning us.

We're getting negative comments and unhappy tech support calls from users such as: "Ever since you put the new system in, I can't get my job done. Please fix it. Just wondering if anyone else is seeing this problem.

I'd ask about the Gateway logs too, but due to it's immediate display, I'm guessing nothing would have been logged on that end. Problem is that there are so many false-positives in the logs that it's so hard to correlate to the actual problem. I'm just happy that we found yet another workaround. At least our users won't be dead in the water, and we won't be asking them to "rebuild their machines" Is this related to drop down menu or pop up window focus?

I applied this but doesn't seem to be fixed. This was supposed to be done on the client side, right? JohnnyNguyenPP : This is not related to the drop down, but can be quite disruptive as it will literally prevent the user from connecting until that process is followed. So, I just recommend you keep it in your back pocket, my guess is you're going to see it in your environment as well. Same issue here. Users with using our RDP hosted apps that have dropdown menu options.

I'm experiencing this myself in our financial system. It's driving a few staff absolutely nuts as it's making the apps appear slow and unresponive. Any word on a patch? Friday, May 25, AM.

Full screen Remote Desktop seems to be fine. Also screen updates aren't always correct, so your mileage may vary. Clearly, rolling back mstsc. I find myself pouring through Microsoft patches to try to figure that out Friday, May 25, PM. Edited by rm Friday, May 25, PM. From my experience, your better off rolling back the update than trying to replace RDP files with older versions.

So here is something odd. I wanted to submit feedback to Microsoft using the feedback hub. When I was in screen capture mode in the feedback hub the drop down menus worked, as soon as a stopped capturing the drop downs did not work.

That's ridiculous. But you should still be able to delay the update for up to a year if wanted. This way your are still on the secure latest RDP just not the latest feature. I remember while back replacing RDP files and an update down the road caused some strange issues we couldn't track down and had to backtrack.

Sometimes I forget to go back and undo the workarounds. I think it was the RDP minimize window freeze issue in windows 7. Hope this helps. I look forward to hearing back, thanks! Yes, I am talking about something delivered through Windows Update. I expect it to work the same way as the fix for the RemoteApp issue that came out a few days ago.

Sunday, May 27, AM. We never had this issue with earlier Win10 Versions we rolled back to Can someone from Microsoft please respond to this? Sunday, May 27, PM. I'm a novice user and haven't the time to read all the above.

Wouldn't know what it means anyway. However since upgrade to my computer is running very slow or hanging. Haven't any idea what this means but it doesn't seem normal. Hope MS gets this fixed soon. This is specifically an issue with the MSTSC Program, if you are having issues on your machine then this will be a local issue and nothing linked to this thread.

Here's a direct download for it, have you tried it? Monday, May 28, AM. Also I'm pretty sure someone from microsoft wrote in the other thread, that this fix is already implemented in , and we still have the same bug in Edit: I just set up a VM and installed KB and it actually fixed our problem : Thank you GTMERP for the tip!! You are correct. It is implemented in the Insider build If you have access to that, you can probably grab the files from it, however the actual installable KB is not yet available for GA of Monday, May 28, PM.

It is implemented in the Insider build If you have access to that, you can probably grab the files from it, however the actually installable KB is not yet available for GA of Maybe they will include it with the June Update :. Please make this available as a standalone patch.

Tuesday, May 29, PM. To support this. Please remember the PR disaster you have created for us and yourselves. Anxiously waiting for the patch : You guys have been great keeping this thread updated. I could not wait for updates any longer I updated to the latest windows insider build that has the fix for the Z ordering issue. Copy the below and paste into notepad and save as a.

Oodog, Haha love it when a community comes together! How would you deploy this through GPO? So I'm curious if you sign up for the Insider Preview just to get this fix applied, does that mean you're tied to the program and will continue to be on pre release status, or is there a way to opt out of the program and tell Microsoft that you don't want anymore hot steamy piles of update goodness?

Instead of downloading from URL how would you copy from a server share path? This is why we have been so adamant about getting a patch pushed out by Microsoft. We tested this over the weekend and it resolved all the issues we could reproduce. We're hoping for feedback today, sent the information before this morning and so far.

Now if Microsoft would only release the update to the general public or make an intermediate patch, life could get back to normal. I too am one of the many admins having to deal with this issue. We're managing just over external customers for which we have zero control over their systems. We are getting an earful daily and the call frequency is increasing as version is being installed. Nothing new to those that are following this thread closely Has there been any update on this?

We have disabled the GPO mentioned at nauseam above which did fix the drop down issue for us. The problem is some apps open minimized now. I have been waiting since early May for this Hot Fix. Where is it? This is beyond frustrating and is just ridiculous at this point. My understanding of the issue is that it's a z order issue, where it sounds like mstsc.

Since it's an issue with the layering on the client side of things, the client needs to receive the fix. It's a pretty sad and vicious cycle we're stuck in. This has been by far the most frustrating issue we've ever dealt with regarding RemoteApp. We can fix the issue by simply rolling the local client files back to version or earlier.

Why couldn't Microsoft just release a hotfix months ago that rolls the mstsc. Why are we forced to work with broken software when an earlier version works fine? Call me crazy, but Microsoft, your first priority should be keeping your software functional. If you have to roll back a few new features to get us and our end users happy, don't you think you'd be in better standing with your customers? This has been just insane.

This issue is not an annoyance, it actually makes it impossible for people to do their jobs. This makes them question their decision to host with us using RemoteApp, and could potentially cost your partners revenue. Microsoft, if you want to be leading the way on Cloud, your software has to work. It has to be tested. It has to allow people to do their jobs.

This cannot continue to happen! Wednesday, May 30, AM. I can confirm that in our case anyway , build corrects the issue. Wednesday, May 30, PM. Hi I confirm that build and rdp I can now activate Remotefx on the server. I can't enable Remotefx until I know users can actually get access to the patch. I'm really really hoping they release this as a stand alone patch. Microsoft - please don't put me in a position where I have to tell folks "at some point over the next couple months this will be fixed for you".

Please release a hotfix. Yes, Please release a hotfix! We shouldn't have to wait for a new build of Windows for this to be fixed. What is the link for rdp Hate to get sentimental, but I'm really going to miss you guys when this is over lol! Nothing brings folks together like Microsoft technical support! Boa Tarde Pessoal! The two files are called mstsc. Change Permissions.

Hey guys, Since Microsoft isn't providing a patch, we decided to patch it ourselves. We just spruced it up a bit for our clients, signed it, and packaged it in a runnable EXE. Also, renaming would actually throw an error anyway, if a bak already exists I understand you might be skeptical running this not knowing what it is, so I won't be offended if you don't download it and try it. We're not doing any shenanigans : P.

S: Please run As Administrator. MessageBox]::Show 'System is already on correct version no further action required. MessageBox]::Show 'Fix has now been applied. At this point it's "the People vs. Search the community and support articles Windows Windows 10 Search Community member. Hello, my laptop has been trying to install this update for more than 2 days. I have ran the update troubleshooter, no help I have downloaded the SSU no help This thread is locked.

You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. DaveM Independent Advisor. Hi Garry Your Windows is a bit out of date, since you are still on version , version has been released, you should go straight to that version to bring your system up to date and make all previous updates obsolete.

How satisfied are you with this reply?



0コメント

  • 1000 / 1000