cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 7

Low refreshrate on Windows 10 ver.1709

Jump to solution

Good afternoon
After 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.

1 Solution
Level 12

Great news! We now have a Beta release, that fixes this issue: Dameware 12.1 Beta 1 is now available

View solution in original post

109 Replies
Level 7

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.

0 Kudos
Level 7

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!

Level 7

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.

0 Kudos

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.

0 Kudos

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?

0 Kudos

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.

0 Kudos

It would be good to know if will takes weeks, months or years to get this fixed.

In April we are deploying 1709 to 5000+ computers.

If this is not fixed by then we have to find Another alternative.

This is something we dont want to do because we Think that dameware is a good Product but this bug makes it useless.

0 Kudos

We have a super strict "do not promise timelines" policy.

I am glad, that you like the product and agree, that this is a serious issue, that needs to be fixed ASAP.

0 Kudos

Dealing with this issue since 5 months is not what i call "fixing it ASAP".

Just ridiculous that its taking so long.

Every software development company should test their software with insider preview builds early to avoid such problems.

I don't want to think about what new problems will come with build 1803 & DameWare...

We have lost our trust to Solarwinds, if they at least could show some proof that they are working on it.

They could present some kind of beta

With this silence maybe they will never fix this issue.

0 Kudos

Hi- what's the best way for me to get an update on this? Is there a newsletter or support bulletin I can subscribe to? Our organization would like to be notified as soon as a new release that fixes this is out.

Thank you-

-Tom

Hi Tom,

simply watch this page on THWACK: What Are We Working on for DameWare - Updated November 27th, 2017

I'll update it, once we ship the fixed driver.

Milan

0 Kudos
Level 7

noticing this  on 1709 as well .  If there's any workaround will appreciate it .

0 Kudos
Level 7

Just noticing it appears that on Win10-1709 at least Dameware no longer see's multiple monitors either.

0 Kudos

hi James, were you able to reproduce it on multiple Win10-1709 PCs? Anyone else seeing this?

0 Kudos
Level 7

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.

0 Kudos
Level 12

Microsoft changed the display driver architecture in their v1709 and that created problems for DameWare. We're fixing this issue now.

0 Kudos

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

0 Kudos

When can we expect a solutions on Dameware problem on windows 10 1709?

0 Kudos

Any update on when this issue will be fixed?

0 Kudos

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