Главная » Linux

Rdpwrap windows 10 19041

Содержание
  1. [Not Listening] on v.10.0.19041.84 #1165
  2. Comments
  3. shardy-uk commented Sep 21, 2020
  4. affinityv commented Sep 21, 2020
  5. TBoneTheOriginal commented Sep 21, 2020
  6. ThoseITGuys commented Dec 8, 2020
  7. Что делать, если не работает RDP Wrap после обновления Windows 10
  8. Способ 1: Замена файла конфигурации
  9. Способ 2: Настройка в «Редакторе групповых политик»
  10. Не работает RDP в целом
  11. Request for Version 10.0.19041.84 (x64) #1004
  12. Comments
  13. EdwardJB commented Feb 21, 2020
  14. omove commented Feb 21, 2020
  15. Atifati commented Mar 4, 2020
  16. TrueXakeP commented Mar 4, 2020 •
  17. TrueXakeP commented Mar 4, 2020 •
  18. affinityv commented Mar 5, 2020
  19. phongtran7 commented Jun 8, 2020
  20. dmcdivitt commented Jun 8, 2020 •
  21. dmcdivitt commented Jul 21, 2020
  22. vmpcitmano commented Aug 6, 2020
  23. dny238 commented Sep 8, 2020
  24. nfero68 commented Oct 7, 2020
  25. eliseozavala commented Dec 24, 2020
  26. babbarvarun commented Feb 26, 2021
  27. 20H2 Build: 19041.789 Not working #1314
  28. Comments
  29. vgisbert commented Feb 3, 2021
  30. vgisbert commented Feb 3, 2021
  31. mariopedroSpo commented Feb 3, 2021
  32. nagyimre1980 commented Feb 3, 2021
  33. yuasa54 commented Feb 3, 2021
  34. snipper12343 commented Feb 3, 2021
  35. snipper12343 commented Feb 3, 2021
  36. MarcinWerra commented Feb 3, 2021
  37. nagyimre1980 commented Feb 3, 2021
  38. emanuelvittar commented Feb 3, 2021
  39. vgisbert commented Feb 3, 2021
  40. dmcdivitt commented Feb 4, 2021
  41. vgisbert commented Feb 4, 2021
  42. malicon commented Feb 4, 2021
  43. Lux-91 commented Feb 11, 2021
  44. MarcinWerra commented Feb 11, 2021
  45. lha314981 commented Feb 14, 2021
  46. owencamilo commented Feb 16, 2021
  47. MarcinWerra commented Feb 16, 2021
  48. lha314981 commented Feb 16, 2021 •
  49. MarcinWerra commented Feb 17, 2021
  50. lha314981 commented Feb 17, 2021 •
  51. MarcinWerra commented Feb 18, 2021
  52. Mindaugas85 commented Feb 22, 2021 •

[Not Listening] on v.10.0.19041.84 #1165

Comments

shardy-uk commented Sep 21, 2020

Running an install on a new PC termserv v.10.0.19041.84 and ran standard install.bat, followed by autoupdate.bat using the latest version from asmtron which completes with the below results:

Automatic RDP Wrapper installer and updater

[+] TermService running.
[+] Found listener session: AllowTSConnection (ID: 1).
[+] Found windows registry entry for «rdpwrap.dll».
[+] Found file: «C:\Program Files\RDP Wrapper\rdpwrap.ini».
[+] Installed «termsrv.dll» version: 10.0.19041.84.
[] Read last «termsrv.dll» version from the windows registry.
[+] Current «termsrv.dll v.10.0.19041.84» same as last «termsrv.dll v.10.0.19041.84».
[] Start searching [10.0.19041.84] version entry in file «C:\Program Files\RDP Wrapper\rdpwrap.ini».
[+] Found «termsrv.dll» version entry [10.0.19041.84] in file «C:\Program Files\RDP Wrapper\rdpwrap.ini».
[*] RDP Wrapper seems to be up-to-date and working.

however, when running rdpconf.exe I receive «Listener State: not listening».

Thanks in advance.

The text was updated successfully, but these errors were encountered:

affinityv commented Sep 21, 2020

Sure, the best clues are, make an exception with Windows Defender or whatever «AV / Security» product you choose to use; my view though is that you shouldn’t be using ANY third party tool for AV / Security as those tend to provide both a false sense of security as well as more potential security holes. Run as a standard user (not admin) for normal things, that alone will save you from most problems and for sure practice safe computing!

Oh, and you must have a trusted 3rd party INI file, the stock project one doesn’t cover many if any versions of Windows in use today (or it shouldn’t).

Please don’t turn off Windows updates either, delay feature updates as long as you can, but you need security updates enabled as Microsoft is so bad that there is regularly many critical security fixes every month!

TBoneTheOriginal commented Sep 21, 2020

Same issue here — I got it working by replacing the rdpwrap.ini file with this one:

ThoseITGuys commented Dec 8, 2020

my issue was that it would want the remote user to kick off the local user.

I tried the INI suggest above but once implemented. the remote user (seperate account on the PC) logs in and the current local users screen changes to the remote user desktop and they cannot move or anything. They can watch what the remote user is doing but they cannot move until the remote user disconnects then they see their user desktop again

Читайте также:  Sketch app ��� mac os

Что делать, если не работает RDP Wrap после обновления Windows 10

Способ 1: Замена файла конфигурации

Проблемы с работой рассматриваемой программы возникают вследствие обновлений системной библиотеки termsrv.dll. Под каждую её версию RDP Wrap нужно конфигурировать заново. К счастью, разработчики приложения заботятся об этом сами и после каждого мажорного апдейта выпускают новый конфигурационный файл. Алгоритм его замены выглядит следующим образом:

    Перейдите по ссылке в репозиторий приложения на GitHub.

Репозиторий на GitHub
Откройте каталог res двойным щелчком левой кнопки мыши. Найдите внутри ссылку с именем rdpwrap.ini и кликните по ней правой кнопкой мыши. Выберите пункт «Сохранить ссылку как…» (в других браузерах – «Сохранить объект как…» или похожее по смыслу).

Сохраните файл rdpwrap.ini в любое подходящее место на компьютере.

После запуска списка служб найдите запись «Службы удалённых рабочих столов», выделите её и нажмите «Остановить службу».

Далее откройте «Проводник» и перейдите по следующему адресу:

C:\Program Files\RDP Wrapper

Скопируйте полученный ранее rdpwrap.ini и вставьте в эту папку.

Подтвердите замену файла.

Перезагрузите компьютер, после чего откройте монитор враппера с именем RDConfig.

Проверьте строку «Listener» – если надпись в ней гласит «Fully supported», проблема устранена.

Данный метод является предпочтительным, и к следующему следует прибегать только в случае отсутствия его эффективности.

Способ 2: Настройка в «Редакторе групповых политик»

Пользователи Windows 10 редакций Профессиональная и Корпоративная могут решить рассматриваемую проблему настройкой определённого параметра в «Редакторе групповых политик».

    Вызовите средство «Выполнить» (шаг 3 Способа 1), в котором введите запрос gpedit.msc.

Перейдите по следующему пути:

Конфигурация компьютера/Административные шаблоны/Компоненты Windows/Службы удаленных рабочих столов/Узел сеансов удаленных рабочих столов/Подключения

Дважды кликните по политике «Ограничить количество подключений».

Установите положение «Включено», после чего измените значение максимального количество подключений на 999999 . Сохраните изменения последовательным нажатием на кнопки «Применить» и «ОК».

Закройте «Редактор групповых политик» и перезагрузите компьютер.

Описанная выше манипуляция позволит решить проблему, но является потенциально небезопасной, поэтому используйте её в самом крайнем случае.

Не работает RDP в целом

Порой вышеприведённые действия не приводят к желаемому результату. В этом случае отметим, что скорее всего дело уже не во враппере и библиотеке. Действуйте так:

    Сначала проверьте параметры брандмауэра, как системного, так и стороннего, и разрешите в нём соединение по РДП.

Урок: Настройка брандмауэра на Windows 10
Также стоит проверить состояние портов – не исключено, что требуемый для работы нужного протокола просто закрыт.

Подробнее: Как открыть порты на Windows 10

  • Ещё раз проверьте редакцию целевой «десятки» – подключение по RDP не поддерживается в Windows 10 Home.
  • Рассматриваемый тип соединения может не работать из-за повреждений соответствующих системных файлов. Для начала проверьте, не завёлся ли в вашей системе вирус.

    После этого проверьте целостность компонентов ОС и восстановите их одним из возможных способов, если в этом появится необходимость.

    Урок: Проверка целостности и восстановление системных файлов в Windows 10

    Теперь вам известно, как нужно действовать в ситуации, когда RDP Wrapper перестал работать после обновления Windows 10, и что делать, если подключение по этому протоколу не работает в целом.

    Request for Version 10.0.19041.84 (x64) #1004

    Comments

    EdwardJB commented Feb 21, 2020

    It’s been mentioned but I want to make a formal request for this. By the way, is there a process for finding the ini values yourself? I’d prefer not to just ask others.

    The text was updated successfully, but these errors were encountered:

    omove commented Feb 21, 2020

    Atifati commented Mar 4, 2020

    Please post files if solution works. Thanks.

    TrueXakeP commented Mar 4, 2020 •

    Offsets for 10.0.19041.84 booth x86 and x64 (so you can change title of this issue) but tested only with x64:

    TrueXakeP commented Mar 4, 2020 •

    . linked in the readme.

    affinityv commented Mar 5, 2020

    Updated rdpwrap.ini file with above sections.

    phongtran7 commented Jun 8, 2020

    [10.0.19041.84]
    LocalOnlyPatch.x86=1
    LocalOnlyOffset.x86=B46B9
    LocalOnlyCode.x86=jmpshort
    LocalOnlyPatch.x64=1
    LocalOnlyOffset.x64=87611
    LocalOnlyCode.x64=jmpshort
    SingleUserPatch.x86=1
    SingleUserOffset.x86=3AD27
    SingleUserCode.x86=Zero
    SingleUserPatch.x64=1
    SingleUserOffset.x64=0BF0C
    SingleUserCode.x64=Zero
    DefPolicyPatch.x86=1
    DefPolicyOffset.x86=3D7D9
    DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
    DefPolicyPatch.x64=1
    DefPolicyOffset.x64=17ED5
    DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
    SLInitHook.x86=1
    SLInitOffset.x86=66658
    SLInitFunc.x86=New_CSLQuery_Initialize
    SLInitHook.x64=1
    SLInitOffset.x64=1BDFC
    SLInitFunc.x64=New_CSLQuery_Initialize

    Читайте также:  Connecting windows and linux

    [10.0.19041.84-SLInit]
    bInitialized.x86 =CF920
    bServerSku.x86 =CF924
    lMaxUserSessions.x86 =CF928
    bAppServerAllowed.x86 =CF930
    bRemoteConnAllowed.x86=CF938
    bMultimonAllowed.x86 =CF93C
    ulMaxDebugSessions.x86=CF940
    bFUSEnabled.x86 =CF944

    bInitialized.x64 =103FF8
    bServerSku.x64 =103FFC
    lMaxUserSessions.x64 =104000
    bAppServerAllowed.x64 =104008
    bRemoteConnAllowed.x64=104010
    bMultimonAllowed.x64 =104014
    ulMaxDebugSessions.x64=104018
    bFUSEnabled.x64 =10401C

    dmcdivitt commented Jun 8, 2020 •

    This configuration does not work for W10 2004, DLL version 10.0.19041.84 on any of my machines. Editing the DLL does work. At http://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/ toward the bottom in a comment by Krox it says:
    «On Windows 10 x64 2004 you should replcace 39 81 3C 06 00 00 0F 84 D9 51 01 00 на B8 00 01 00 00 89 81 38 06 00 00 90 in the termsrv.dll file»
    This worked on all my machines. Can someone see why the rdpwrap.ini change does not produce the same?

    dmcdivitt commented Jul 21, 2020

    This change did work for me once I recognized I needed to reinstall rdpwrap. Never had to do that before.

    vmpcitmano commented Aug 6, 2020

    This worked perfectly on my latest windows updated windows 10×64 2004 enterprise 19041.423 as on 6Aug2020 with Terminal Services v 10.0.19041.84. Many thanks to the developers and updaters .

    dny238 commented Sep 8, 2020

    The block above worked for me, but only after I made sure it had a blank line at the end of the rdpwrap.ini file.
    Somehow when I copied it, it didn’t put it in there automatically. Hope this helps someone else.

    nfero68 commented Oct 7, 2020

    Thanks this last suggestion, I will try. I realized that everything was fine, but the remote desktop didn’t work. I reinstalled the program and even the remote desktop service stopped! I never had this before.

    I will try the blank line! Thanks!

    eliseozavala commented Dec 24, 2020

    Fix problem for me . ThankU

    babbarvarun commented Feb 26, 2021

    You can’t perform that action at this time.

    You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

    20H2 Build: 19041.789 Not working #1314

    Comments

    vgisbert commented Feb 3, 2021

    The text was updated successfully, but these errors were encountered:

    vgisbert commented Feb 3, 2021

    Thanks for your hard work

    mariopedroSpo commented Feb 3, 2021

    nagyimre1980 commented Feb 3, 2021

    no solution so not good (

    yuasa54 commented Feb 3, 2021

    yeah for now 789 build not in the wrapper ini file. so if you have autoupdater when they update the ini you will have it

    snipper12343 commented Feb 3, 2021

    Can someone post the new INI please?

    snipper12343 commented Feb 3, 2021

    @yuasa54 can you please post your new ini file or copy the lines? thank you

    MarcinWerra commented Feb 3, 2021

    nagyimre1980 commented Feb 3, 2021

    emanuelvittar commented Feb 3, 2021

    It fully works! Thanks.

    vgisbert commented Feb 3, 2021

    Nice reverse engineering job. Thank you.

    dmcdivitt commented Feb 4, 2021

    MarcinWerra’s change worked for me.

    vgisbert commented Feb 4, 2021

    It fully works! Thanks MarcinWerra .

    malicon commented Feb 4, 2021

    MarcinWerra Thank you. It works great.

    Lux-91 commented Feb 11, 2021

    @MarcinWerra there is any guide/tutorial/article where i can try to learn how to update the ini file by myself?
    Thx 🙂

    MarcinWerra commented Feb 11, 2021

    When I tried to create the parameters for the .ini file myself for the first time, I watched the video on Youtube very carefully «Practical reverse engineering (for RDP Wrapper)»
    You can read the issue «How to add support to a new Windows build? How to get the offset for the ini file? #1098»
    or malicon’s answer.

    lha314981 commented Feb 14, 2021

    Single session per user
    doesn’t work
    best regards

    owencamilo commented Feb 16, 2021

    Single session per user
    doesn’t work
    best regards

    MarcinWerra commented Feb 16, 2021

    SingleUserOffset.x64=0CB22

    lha314981 commented Feb 16, 2021 •

    here more precise test

    Читайте также:  Обновление windows 10 20h2 remontka

    in both cases ie
    SingleUserOffset.x64=0CA4C
    and
    SingleUserOffset.x64=0CB22
    setting Single session per user has no effect

    —testing from host computer
    i’m using client 5.1.2600.2180 (distibution client doesn’t connect)

    connecting with user name and password entered In client works as Single session per user set active
    disconected session is reused

    connecting with user name and password entered on logon screen works as Single session per user set inactive
    always new session is opened

    —testing from remote computer
    5.1.2600.2180 and distibution client works the same
    behaviour is as above

    mixing both types of login behaves as Single session per user set inactive

    MarcinWerra commented Feb 17, 2021

    In the rdpconf.exe application, set:

    After that, run the command:
    RDPWInst -r
    (to restart the remote desktop service)

    I tested multi-session per user by connecting using client applications from Windows 10 and XP.

    lha314981 commented Feb 17, 2021 •

    I stand by my opinion
    setting Single session per user has no effect

    however
    Authentication mode works as follows

    GUI authentication only (windows login screen) — enables many sessions for same user, each login creates a new session, disconected sessions are not reused, disconected users should be logged out via (fe.) task manager->users->logoff user

    Network level authentication (client login dialog) — makes that user can open one (mostly) rdp session, disconected session (one) is reused, if there is more disconeccted sessions, then system behaves as above.

    question is: do code which handles «Single session per user» functionality could be patched ?
    if it doesn’t works it is possible that it changes some random code
    so maybe
    SingleUserPatch.x64 set to 0
    see RDPWrap.cpp line 723 and below

    ps.
    p. Marcinie ma Pan już to jakkolwiek ogarnięte, może się Panu uda znaleźć właściwe rozwiązanie
    życzę powodzenia
    pozdrawiam

    MarcinWerra commented Feb 18, 2021

    @lha314981 setting Single session per user has no effect

    I cannot reproduce your problem.
    I tested RDPWrap on dozens of computers with version 19041.789 and it works fine with Single session per user.

    do code which handles «Single session per user» functionality could be patched ?
    if it doesn’t works it is possible that it changes some random code

    Lines 722 to 740 in a5c64a4

    # ifdef _WIN64
    if (!(IniFile-> GetVariableInSection (Sect, » SingleUserPatch.x64 » , &Bool))) Bool = false ;
    # else
    if (!(IniFile-> GetVariableInSection (Sect, » SingleUserPatch.x86 » , &Bool))) Bool = false ;
    # endif
    if (Bool)
    <
    WriteToLog ( » Patch CSessionArbitrationHelper::IsSingleSessionPerUserEnabled \r\n » );
    Bool = false ;
    # ifdef _WIN64
    SignPtr = (PLATFORM_DWORD)(TermSrvBase + INIReadDWordHex (IniFile, Sect, » SingleUserOffset.x64 » , 0 ));
    Bool = IniFile-> GetVariableInSection (Sect, » SingleUserCode.x64 » , &PatchName);
    # else
    SignPtr = (PLATFORM_DWORD)(TermSrvBase + INIReadDWordHex (IniFile, Sect, » SingleUserOffset.x86 » , 0 ));
    Bool = IniFile-> GetVariableInSection (Sect, » SingleUserCode.x86 » , &PatchName);
    # endif
    if (Bool) Bool = IniFile-> GetVariableInSection ( » PatchCodes » , PatchName. Value , &Patch);
    if (Bool && (SignPtr > TermSrvBase)) WriteProcessMemory ( GetCurrentProcess (), (LPVOID)SignPtr, Patch. Value , Patch. ArraySize , &bw);
    >

    With the patch SingleUserOffset.x64 = 0CB22, SingleUserCode.x64 = Zero is patched CSessionArbitrationHelper::IsSingleSessionPerUserEnabled

    But the strangest thing is that, with the patch disabled by SingleUserPatch.x64 = 0, it also works fine for single session per user and multi session connections.

    PS. @lha314981 🙂 Może prędzej się dogadamy po polsku. (Proszę odezwać się przez Messenger https://www.facebook.com/WerraMarcin/)

    Mindaugas85 commented Feb 22, 2021 •

    So at least RDP Wrapper is working on halfway.
    RDP multisession working, but not printer redirection 🙁 and it’s very saaaad.
    When copying old rdpwrap ini file — printers working, but not RDP multisession,
    if but I changing ini file to support [10.0.19041.789] Windows 10 20H2 multisession — after restarting pc — printers are disappearing, only leaving to redirect «Pdf creators», One notes and others non-real printers.
    Termsrv.dll I haven’t modified.

    INFO UPDATE
    I forgot to mention one thing,
    When I’m using unsupported rdp ini file, all printers redirecting,
    then updating ini file after closing and saving file without pc restarting.
    then and RDP working with multisession and printers redirecting, BUT BUT BUT — when i’m doing OS restart. redirected printers disappiering and working onlu RDP multissession 🙁
    IN RDP config windows -showing that everuthin green and ok.

    • Оцените статью
    © 2024 Советы по настройке компьютера