Good afternoonAfter installing WINDOWS 10, and upgrading it to version 1709 when connecting DAMEWARE, low FPS is observed on these computers. The quality of the connection is 1Gb. On other computers, there is no such problem.
Great news! We now have a Beta release, that fixes this issue: Dameware 12.1 Beta 1 is now available
I have noticed the same issue. I thought it was just me or the system lagging. Its annoying but I can deal with it for now with as few systems we have running 1709. As that number increases though it could become more of an issue.
Microsoft changed the display driver architecture in their v1709 and that created problems for DameWare. We're fixing this issue now.
Any update on when this issue will be fixed?
When can we expect a solutions on Dameware problem on windows 10 1709?
I am not allowed to answer this question. Have you reached out to our support? We have a workaround, that improves the behavior a bit:
IN DMRC -> Top Menu -> View -> click Default Host properties
Display Options tab -> Force 24bit display
Mirror Driver tab -> Force 24bit display
Remote Options tab -> Desktop Effects -> disable all desktop effects
Change the compression level to 9; Scan Blocks to 1 and Delay between Scan Block Update to 250; Check if slow link optimization is checked.
Let me know, if that helps a bit. We'll work on a new mirror driver in the meantime and provide a fix ASAP.
Milan
The settings suggested helped with the clipping issue of Win 10 1709.
Hello,
I am having the same issue. Is there an update?
Hi
When can we expect a fix for this problem, we are now Rolling out 1709 to 7000+ computers
If we dont find a solution for this soon we will have to start looking at alternatives
Best Regards
hmmm, any News on this?
we are doing the rollout, too.
i hope to see a fix soonish, the product is quite useless with such latency.
It's been 4 months since the problem was discovered. No fix has been made since ?
Please, give us news about this issue and release an update as soon as possible to solve this.
It becomes problematic for our computer park of more than 1500 computers.
Thank you in advance
Best Regards.
Just noticing it appears that on Win10-1709 at least Dameware no longer see's multiple monitors either.
hi James, were you able to reproduce it on multiple Win10-1709 PCs? Anyone else seeing this?
noticing this on 1709 as well . If there's any workaround will appreciate it .
Why are Solarwinds so slow fixing the Windows 10 1709 problem, it's over 3 months since the bug founded.
Why waiting to fix this problem in a major update .
I think so many customers are left behind.
Please do something.
Trust me, this belongs to the top 3 most important things, we're working on now. Also it is the most expensive, out of those 3.
Same issue for us on windows 10 1073 and 1709 versions. Do you have an estimated time frame of when an update will be available?
Unfortunately, I am not allowed to speak about ETAs. I can say, that this is a well known issue, that we need to address and will do so in a future release.
Having the same issue here. About to roll out Windows 10 and this lag with Dameware is killing us. This is a very critical issue! We just purchased Dameware!
I am also experiencing this with Windows 10 1709 computers. I also noticed that there was only one monitor in the monitor list even though the computer had 3 screens in display settings. In display settings I changed the main display to another monitor and after doing that all of the monitors listed in Dameware's drop down list. After switching the main display back to the original display I could still see all of the monitors and switch to them. I followed Milan's above suggestion to change Default Host Properties and it helped for a minute but after switching monitors I started experiencing screen refresh issues again.
A majority of our computers are on Windows 10 1703 and there is no issue between the machines and Dameware.
Quick and dirty workaround is to disable MRC's mirror driver. When you launch DMRC, fill your user ID and credentials and right under credentials is a checkbox saying "Use MRC's Mirror Driver if available" - simply uncheck and connect.
No noticeable difference for me, issue is still there.
Minimal difference. Still a lag with Windows 10. I just talked our whole department into purchasing Dameware! Didn't realize there would be this issue with Windows 10.
Are there any updates on this issue? The same thing happens on Server 2016 as well
Bennett, we're seeing a good progress on a new driver. Once we have the driver signed and integrated with DameWare, I'll reach out to this group to do some early customer testing.
6 months have gone and still no solution.
Just tell us, If you do not want to develop this product anymore, don't fool with customers.
All, completely understand the frustration, but let me quickly introduce myself. I just returned to SWI a couple of months ago and lead product management and strategy for our Systems Management and tools portfolio of products and Milan is on my team. In my previous stint here, I was at SWI for 6.5 years solely in product management. I actually was at one time the PM of DameWare as well back in my earlier days. To give folks an update on this front, while I don't have a firm timeline, we have a team actively working on this right now including consulting with an external firm which specializes in kernel level drivers for OS's. We are getting much closer to have something ready, meaning months. When we do have some beta or RC level code, please let me know if you are interested in helping us kick the tires. Also please feel free to contact me if you wish to discuss at brandon.shopp@solarwinds.com.
Still no update yet?
New model's are coming out that only support 1709 and above thus being unsupportable with Dameware...
We have Surface Book 2's being deployed to our fleet which will be unsupportable via Dameware
We're incorporating the new driver to the DameWare MRC build and will soon start testing it. We're be running Beta with customers under active maintenance. If you're interested in Beta, send me an email to milan.hulik@solarwinds.com
We're getting really close to having a Beta build. New mirror driver is now integrated with DMRC and it connects to Win10 machines! Finally. We now need to resolve small performance related issues and then ship a Beta build. Stay tuned! I received tons of requests from you to participate in our Beta program. As soon as we have Beta out, I'll post registration information to this thread as well. Thank you for your patience. Milan
HI Milan,
it has been an week since your last post, can you post an update of the current status?
Damian
I do not have anything exciting yet. Saw a demo today, it worked. Team has to fix a few bugs and make sure that we give you stable build with no regression issues. So we'll also have to do a bit of testing before we launch beta.
Hi Milan
its been over 3 weeks since your last progressive update. Still waiting for beta build to test on our end so we can upgrade our systems to 1709...
Same Problem here. We need a supported Version very urgent. We have currently 1400 Computers with Windows 10 - 1709 or 1803. Can we get an Beta Version or something?
I will throw in my hat also. Windows 10 and Windows 2016 lag hard, we would really like a fix also.
Just wanted to see if there is any status updates on this fix. We really want to get Win 10 v1709 out the door and this bug is preventing us from rolling this out.
Thomas, we're very close to Beta, meaning hours/days. I'll post Beta registration link here on THWACK for anyone who is interested.
I am :-)
Yes please, I've been following this thread for some time now and have been waiting for a fix/workaround.
I am
Ok. First, thanks to you Milan, and all the staff who worked hard on this one !...
Unfortunately, I've test DW12-1Beta on my computer few minutes ago and here's what I experienced :
From my Windows 10 surfacePRO4 I tried to reach my other Windows 10 - lenovoX1 Tablet, which has three (3) displays.
The first is the tablet itself, the second and the third are my 2 HP displays
From my host, I could connect, what I also did with DW12, but I could not get my displays correctly.
When I selected the first display, I got the Tablet (which it was correct). But when I clicked 2 or 3, I got the 'V' disposition (which I had by clicking 'V' too ...)
This is a known issue in the Beta1 release. We'll fix it either in the next Beta or RC build.
what about centralized instalation? we don't have licence for per seat, only DameWare Remote Support Centralized Server...it can only use evaluation 14 days version...
Any answer to this question asked almost a week ago?
Apologies for a timely response. I was on a PTO for couple of days and now I found your comment.
Purpose of Beta 1 is to test the new mirror driver against Win10 in customer's environment. We're now logging and fixing a few issues and based on how much impact the fixes will have, we'll release either Beta 2 standalone to run another test, or better case - release candidate (RC).
RC would be centralized and standalone, available via customer portal for all customers under active maintenance.
I installed the beta and removed the productive agent on testmachine and installed the agent with default settings. Is there a need to to this or can I use the agent from version 12.0.3.xxx?
Performance seems to be better. The session is more responsive. But I still have some lags and sometimes not an actual view from the client (need to use send refresh option).
If I grab a application windows and move it fast, it get distorted.
Some feedback here:
Just tested with a small team so far before releasing it to more users to test:
Found if Mirror Driver either setting Force 8,16 or 24 bit Display is checked the screen displays black or distorted like the image posted:
This is found under View > Default Host Properties > Mirror Driver Tab
And then theres the lockscreen freezing during login transition to the desktop. Which a disconnect and reconnect fixes. This is stated in your beta notes as a known issue. More of a annoyance then show stopper
Any ETA yet when your updated version of the beta will be released?
Hi Patrick, thank you for the feedback. We're shooting for a GA by the end of this quarter, but there are some other initiatives going on, that might affect my current schedule. I cannot commit to anything now.
It now doesn't work with windows 7? I just get no screens at all when connected.
My Beta 1 trail has expired. Do you have a newer beta to use, or do I need to revert back to the old software?
hey Guys
My testers have been reporting back some weird behaviour with the beta agent, this may be due to only testing the beta agent with using MIRC 12.04
These are:
chatting text in common applications from remote machine is not appearing on local machine
Crashing on remote computer
I wanted to try test the 12.1 beta agent with using MRC 12.1. Problem is to test this properly in our environment we want to be able to install MRC 12.1 in centralized mode to connect to our centralized server through AD accounts
I dont see this option anywhere. Usually this asks you upon the install process like our precious version
Is there another way to get this to install so when you launch it it pops up with centralized server authentication?
It seems I can only test this with evaluation mode
Even if the evaluation mode works flawlessly its useless to us unless we can get it to connect to our centralized server
This is what I mean by not seeing any option to install in Centralized mode:
Any updates?
Are there any updates? We need a stable Version to Rollout.
Since the Beta1 launch, we have added multi-monitor support to the new mirror driver, added different bit modes, fixed security vulnerabilities and fixed FIPS mode.
We're now working on 4k resolution support and TLS1.2 support for the over-the-internet connections.
milan.hulik
Still ETA on release that update you just mentioned is this correct?
pguerrisi, I am not allowed to communicate timelines. Since the Beta1 launch, we have fixed most of the issues present in Beta1 and finalizing features, that were not present in Beta1. I'd like to give you stable Beta2 build.
So coming across an issues in our test group here at the office. 12.1 responds great with Windows 10 and I notice the difference from each software version but unfortunately, 12.1 Beta 1 seems to lock up the screen on my end while it still displays my mouse moving on the end-users computer. Disconnecting and reconnecting will allow the connection to be reestablished. This is caused but using the 12.1 Beta 2 on my desktop and 12.1 Beta 1 on the end users.
If we setup 12.1 Beta 2 on my desktop and the end users, we get an issue where the screen freezes on "Initializing Desktop, please wait."
We never had this I issue with 12.0.5 on our old systems so I figured it may still be a bug that's being worked on.
yes, same Problem here. It freeze at "Initializing Desktop, please wait." on Beta2. With Beta 1 there is no problem.
I've got the same problem with version 12.1 beta 2 connecting Computer with Windows 10, but not all the Windows 10 were freeze at "initializing" screen. which is still confused me.
when i trying to remote a computer after installed the DMRC 12.1 Beta 2 on my laptop, there is a selection popped up that you can choose whether you want to install some update on your remote computer.
if you choose not to install the update, the performance would remain slow. and when you choose to install the update, the Freeze at "Initializing" happens.
here is the findings from the test I've just been done minutes ago.
there are 2 computers with Windows 10 that i had chose for the test.
Computer A: Frozen at the "initializing"
Version:1709
OS Build: 16299.611
Amount of items existing in the folder C:\Windows\dwrcs\: 97
Has been connected by other versions of DMRC Previously?: Yes, DMRC 12.0.5.
Computer B: not frozen at the "Initializing.
Version: 1709
OS Build: 16299.309
Amount of items existing in the folder C:\Windows\dwrcs\: 43
Has been connected by other versions of DMRC Previously?: No.
after i had copied and replaced the folder C:\Windows\dwrcs\ from B to A, and tried to remote Computer A using DMRC, it's worked as expected, the refresh rate is acceptable.
apparently I am not sure how these software works internally, that is why it is still confused me, hope the input helps you to figure out and fix the problem. Thank you.
and it is appreciated that if you could send me an update when there's any useful updates or any beta/official version released.
already reported by another customer in this thread: MRC 12.1 Beta 2 Feedback
please try the described workaround (Uninstall Service on remote machine, reinstalled service)
Thank you for the reply, I had tired the suggested operation on my test machine and It is worked, no longer Freeze at the Initializing Desktop step.
I can use the way as a temp solution for a while, but I’m still looking forward an Official New Version.
Thanks.
Snow Cao
T +86 10 5922 1392
M +86 186 1065 0765
Any status on when the GA of 12.1 will be released.
The release candidate for DameWare 12.1 is now available in the customer portal for download. To remind folks, RC's are fully supported and can be deployed into production.
Doesn't work, says there's an issue with the installer package for the x64 installer.
Error from event log: Product: DameWare Mini Remote Control x64 -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: StoreStandaloneConfig, location: C:\Program Files\SolarWinds\DameWare Mini Remote Control x64\, command: "" -storestandaloneconfig
I'm looking at our Customer Portal and don't see the 12.1 release, just the 12.0.5. How do we go about getting version 12.1?
I tried to install the RC 12.1 but during install I Need to enter a valid License, which I don't have.
Eval is exipred due to earlier Tests with beta. How do I reset the eval lic?
Either use another machine or you can ping me via DM or email and I can give you an update evaluation/trial key.
Does anyone else confirm problems with the "Switch RDP Session" function on RDS Windows Server 2016?
Loading the initial desktop and switching to another session is very slow. Sometimes/mostly even the Dameware service crashes and has to be started manually on the RDS System again.
The problem occurs with the new 12.1 RC and even with the previous version. We thougth that it would get better with the new update.
Do you know if you have ever opened a support ticket on this previously? If so, do you happen to know the case number and I can dig into things on this side as well.
Is there any release notes for the release candidate 12.1 version?
Yes here you go - Dameware Remote Support Version 12.1 Release Notes - SolarWinds Worldwide, LLC. Help and Support
Tested RC 12.1. Very good Performance and Response while remote.
Some disturbing Things are still here.
Display refresh rate (how I understand it) is slow. Sometimes I can paint on screen
Sometimes the remote session is like hanging. No Chance to interact with remote Computer. Need to disconnect and reconnect again.
Have you opened any support tickets yet on this issue with the RC so we can dig into it further? If yes, can you send me or post your case number please?
If you have tried searching online and not found the solution of the file explorer in windows 10 computers so, you can try to fix this hurdle and the file saved in your operating system.
We're still using DameWare 11 here but I managed to minimize this issue by simply setting "Scan Block" to 2 and disabling all Desktop Effects.
This should be resolved with version 12.1 of DameWare which is now generally available to customers with active maintenance.
So 12.1 is not a version where we'd have to buy new licenses and can use the one for 11.1 still?
If you are under current maintenance, yes, the new version should be available in the customer portal. We do not make you pay for new version upgrades, you just have to be under active maintenance.
