DirectAccess Client not connecting without error code on Windows Server 2012 R2 and Windows 8.1

Hello,
we are currently migrating from Windows Server 2012 to 2012 R2 and are not able to get the new Direct Access Service up and running. Our goal is to establish DirectAccess connection for a handful of clients using the IPHTTPS-adapter on the default port 443.
Errors:
There is actually no error showing up. It seems the infrastructure tunnel cannot be created but none of the IPv6-transition adapters is connecting (teredo and 6-to-4 are down) and the IPHTTPs adapter gives no informations about a problem:
>Get-DAConnectionStatus
Status    : Error
Substatus : CouldNotContactDirectAccessServer
>Get-NetIPHttpsState
LastErrorCode   : 0x0
InterfaceStatus : Failed to connect to the IPHTTPS server; waiting to reconnect
Setup:
Our setup is a virtualized Windows Server 2012 R2 Standard running on Hyper-V. It is located behind a NAT having the Port 443 mapped to the server. The only role installed after the basic install is RRAS including DirectAccess and VPN. The assistants completed
successfully (running the configuration for DirectAccess and VPN). Operation Status says everything is green und working (for multiple days in the meanwhile). A previous direct access installation (on a different machine running Windows Server 2012) has
been removed before installing the new server. The new installation is using a different router, so this might also be the cause of a problem.
The client is a Windows 8.1 notebook located outside the company network accessing the internet through another NAT-device. The client has been able to connect to the previous DirectAccess setup but has never been able to establish a connection after the
setup of the new Direct Access server. The device has no outbound constraints concerning the NAT-device and is only running the integrated Windows Firewall.
Diagnosis:
So far I've done some basic DNS and connectivity checks. The DNS-name can be resolved correctly and the router even responds to pings. The port forward is working and HTTPs connections are generally possible (temporarily routed the port to
access the NLS-Website located on the server, which worked fine).
Network monitor shows that both computers are communicating, traffic on the expected Port 443 is incoming on the server and responses from the server reach the client.
Opening the IPHTTPs-url and in an endless page load. Sometime the browser page closes but I've never seen any result. Using telnet on the port shows that the server is accepting connections. I've even build a small test application that does a GET-Request
on the URL returning HTTP-200 and no content.
I'm currently running out of ideas what to do and since no error occurs this is kind of a bit frustrating. Any help appreciated.
Regards
Matthias

Hi,
In addition, have you disabled the DA client components on the DA client? If no, please also check
the settings on the Name Resolution Policy Table.
More information:
DirectAccess
Client Location Awareness – NRPT Name Resolution
In addition, error 0x4C9 means the remote computer refused the network connection. It may be due to the invalid
registry or corrupt drivers. For more detailed information, please refer to the link below:
Error 1225 - Error Code 0x4C9
Note:
Microsoft is providing this information as a convenience to you. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Susie

Similar Messages

  • DirectAccess Windows Server 2012 R2 and Windows 8.1 - status connecting

    I've successfully deployed DirectAccess on Windows Server 2012 R2 in a 2 node NLB cluster. Everything in the console is green and I can see clients connecting.
    Windows 7 clients can connect and with the DirectAccess connectivity assistant installed show as connected and I can access resources.
    On a Windows 8.1 client I can access resource and run the troubleshooting tool which reports no errors, but if I look at connections it shows as connecting and the status never changes to connected. Clients work correctly when on the internal network.
    I've looked at available hotfixes, but not found anything for when the status is incorrectly shown.
    Any ideas before I raise a support call?
    James Saunders

    Hi,
    You current information hardly determine which part may occur error, I found the similar symptom on the following third party article, may can give you some help.
    The similar issue third party article:
    Windows 8 DirectAccess client keeps saying "Connecting"
    http://tfs.letsblog.it/post/2013/07/10/Windows-8-DirectAccess-client-keeps-saying-Connecting.aspx
    More information:
    The Network Connection Status Icon
    http://blogs.technet.com/b/networking/archive/2012/12/20/the-network-connection-status-icon.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Error in push sccm client CcmSetup failed with error code 0x80070643 ccmsetup sccm 2012

    i want to push sccm client for all computer i enable automatic side-wide client installation 
     some computer get error code 0x80070643
    ccmsetup sccm 2012 this 
    when i tray manual installation get same error and ccmsetup.exe stopped 

    Duplicate of
    https://social.technet.microsoft.com/Forums/en-US/3bac4677-46b0-4d96-b63d-a819efcc7f35/error-in-push-sccm-client-ccmsetup-failed-with-error-code-0x80070643-ccmsetup-sccm-2012?forum=configmgrgeneral
    Please don't double post.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • REMOTE DESKTOP SERVICES CLIENT ACCESS LICENSES FOR MICROSOFT WINDOWS SERVER 2012 STANDARD AND DATACENTER

    I am using a window 7 professional  service pack 1 and I purchase REMOTE DESKTOP SERVICES CLIENT ACCESS LICENSES FOR MICROSOFT WINDOWS SERVER 2012 STANDARD AND DATACENTER. but  the seller did not send me any installation CD or instruction
    on how to use it.
     Please how can I use it on my window 7 professional  service pack 1.
    Thank you.

    Though Bill is absolutely correct for most CALs, Remote Desktop Services does have its own special licensing server.  I haven't installed one on 2012, yet, but here is a step-by-step guide for 2008. 
    http://technet.microsoft.com/en-us/library/dd983943(v=ws.10).aspx
    Here is a lab guide for 2012 -
    http://technet.microsoft.com/en-us/library/jj134160.aspx
    But, the explanation of your environment begs the question - what are you trying to do?  You say you have a desktop OS and you are talking about Windows Server products.  In that light, your question does not make a lot of sense.
    . : | : . : | : . tim

  • HT1218 i have a windows 8 computer that is not connecting with my time capsule wifi. my other macs and windows 7 systems do connect. is this a firmware update glitch? any suggestions?

    I have a windows 8 computer that is connecting poorly via wifi and my Apple time capsule to the internet. My IMac an another windows 7 based computer are connecting fine. This started 6 days ago. And, the windows 8 machine connects well via a hard Cat-5 connection to the time capsule (I'm using that now) and worked well on a wireless netgrear system over the weekend.
    I'm thinking an automatic firmware update may have caused this or perhaps i need the time capsule to use something other than a default address. Those are just guesses, but I could sure use some help. Thank you.

    It is hard to figure where the issue is..
    Certainly if windows updated the wireless driver that can mess things up no end..
    What update happened 6days ago?
    What TC do you have.. ?? If it is flat one and you updated to 7.6.4 do a factory reset and reconfigure.
    If that doesn't work roll the firmware back to 7.6.1 or even 7.5.2 as these are generally superior to windows.
    There is no update for TC gen5 yet.

  • I am having trouble ejecting a disk that got a code error on it.  I do not know the error code.  I did the restart and hold the mouse down and it ejected. Inserted another disk and this got an error code on it too.  However I can't get this disk to eject

    Having trouble ejecting a disk.  I tried all the suggestions on the help list.  to no avail.

    Was this on the help list:
    1 - open the Terminal application (in the Applications/Utilities folder).
    2 - enter
    drutil tray eject 1
        followed by the Enter or Return key.
    OT

  • ServerManager.exe - This application could not be started. - Windows Server 2012 R2

    Hello All,
    We have a Dell Precision M4800 installed with Windows Server 2012 R2, and we are unable to get the Server Manager working. When we click on ServerManager, the below error occurs,
    Error Message: ServerManager.exe - This application could not be started.
    Action Taken:
    1. Windows Updates, and Windows Security Updates are up-to-date, rebooted
    2. Display Drivers are updated, rebooted
    3. .NET Framework 4.5.2 is updated, rebooted
    Still the same error. Please assist.
    Thank you, Anand
    Anand Franklin

    Hi,
    Thanks for your post.
    Usually, ServerManager.exe error may be caused by:                    
    The registry key of ServerManager.exe is invalid or damaged.
    Computer malware has injected malicious code and modified ServerManager.exe file.
    The ServerManager.exe file was uninstalled by other software.
    The ServerManager.exe file was intentionally or mistakenly deleted by other software.
    The required version of ServerManager.exe file is overwritten by other software.
    There is a hardware failure, such as a bad hard disk.
    You can use the following solutions as the article mentioned to fix ServerManager.exe error:
    http://www.fixerrorhelps.com/fix-pc-error/how-to-fix-ServerManager.exe-error.html
    If all the suggestions did not work, i think we need to reinstall the Operating System.
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • New Windows Server 2012 unable connect to Netlogon Service or update DNS records

    Hi everybody, all of my Windows Servers 2012 decided to collapse after innocuous group policy update that was meant to make user passwords more secure.
    The AD and DNS seem to be functioning "normally", I am able to add new Windows7 and Windows Server 2008 machines to the domain, I can see them in listed in the AD and DNS record are update correctly, however, as soon as I try to join Windows Server
    2012 it breaks.
    The event log is littered on the new server with:
    The system failed to register host (A or AAAA) resource records (RRs) for network adapter
    with settings:
               Adapter Name : {DB7F73CE-E011-4F3C-BEBC-2CE7A871DF51}
               Host Name : CHEETAH
               Primary Domain Suffix : somedomain.com
               DNS server list :
    192.168.0.5
               Sent update to server : <?>
               IP Address(es) :
    192.168.0.15
    The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running
    at this time.
    You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
    and
    Name resolution for the name _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.somedomain.com. timed out after none of the configured DNS servers responded.
    When I try to ping the primary DC (WS2003) it fails, the Secondary DC (WS2012) responds.
    The >nltest /sc_query:somedomain.com on Windows Servers 2012 returns:
    Flags: 0
    Trusted DC Name
    Trusted DC Connection Status Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
    The command completed successfully
    yet it works on all other machines.
    I tried removing 2012 servers from the domain and rejoining - without success. The cookie crumbled when I added two new installations of Windows Server 2012 & 2008 and 2008 worked fine but 2012 showed same symptoms.
    There is one peculiar thing that I had noticed on all Windows 2012 machines, it constantly showing "Workplace Connection - Connecting" in the networks pane on the right side of the screen, which I can't say i ever noticed before.
    Unfortunately, the secondary DC is a multihoming server with Direct Access role - I am not sure if this may play some part but our existing configuration worked for a year now without any problems. Issue appeared when I changed the password complexity rule,
    which boggles the mind. I wonder if there has been some other changes in GPO that did not propagate from years ago and finally comeback to break things.
    Any suggestions would be really appreciated.
    wmin

    Hello Ace, i wish you a Happy New Year! I hope your break was enjoyable and filled with cheer.
    In the end I had to bite the bullet and reinstall all troublesome servers. Your recommendations from above removed some serious problems with the DA and DNS resolution.
    I was able to attach new server to the domain without any problems and begin painful process of rebuild.
    I have promoted TIGER to full DC controller role, but having some issues with replication. Although running >repadmid /showrepl gives positive
    feedback, the sysvol folder on the secondary DC is empty.
    Also there is a couple of warnings in the event log:
    Event ID 4012
    Log Name: DNS Server
    Source: DNS-Server-Service
    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial
    synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server
    for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
    - which has not repeated since 3rd of Jan.
    These events occur on the primary DC every few minutes:
    Event ID 1030
    Source: Userenv
    Log Name: NT AUTHORITY\SYSTEM
    Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Event ID 1058
    Source: Userenv
    Log Name: NT AUTHORITY\SYSTEM
    Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=somedomain,DC=com. The file must be present at the location <\\somedomain.com\sysvol\somedomain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
    (The network name cannot be found. ). Group Policy processing aborted.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Should sysvol folder be shared on the secondary DC? Another interesting thing to point out is that
    \\somedomain.com\sysvol\somedomain.com\Policies\ can be access
    from all other machines except the DC1.
    Cheers!
    kind regards,
    wmin

  • Updates and Hotfixes for DirectAccess 2012 R2 and Windows 8.1

    for some of you who use DirectAccess probably familiar with the following link
    Recommended hotfixes and updates for Windows Server 2012 DirectAccess
    as far as I know and according to TechNet, DirectAccess hasn't change a bit from 2012 to 2012 R2 servers.
    I use DirectAccess on Windows Server 2012 R2 and I'm surprised to see that there is no single update from that list the applicable with either Server 2012 R2.
    if it's true - shouldn't there be a documentation that talks about the differences of the DirectAccess Client\Server from 2012\8 to 2012 R2 \ 8.1?
    I'm asking because I want to make sure those updates are already include or not needed for 2012 R2\8.1 and not "forgotten" or something.
    Tamir Levy

    I was afraid that you'll said that
    I hate to be the annoying guy but take a look at this KB article:
    http://support.microsoft.com/kb/2787534
    Applied to: Windows 8\2012,
    Doesn't Apply to: Windows 8.1\2012 R2
    and - for a fact, doesn't include in Windows 8.1\2012 R2 as this bug still exists in those operating systems.
    another annoying fact - No other update was released for these version yet.
    this example approves that not every hotfix \ updates that was released for 8\2012 before 8.1\2012 R2, is already included in 8.1\2012 R2
    and allow me to add another fact.
    when you configure DirectAccess via the remote access wizard it creates a WMI query called
    DirectAccess - Laptop Only WMI Filter.
    after you create it in Windows Server 2012 R2 - look at the WMI Query and you'll see that by default it doesn't apply to version 6.3! the version for Windows 8.1.
    if you want to add the support for Windows 8.1 you have to modify manually the query which is of course, not supported by Microsoft.
    That is just another symptom that makes me wonder if Microsoft did ANY change or update to DirectAccess 2012 R2
    Tamir Levy

  • Windows Server 2012 Essentials not listed in EasyStartu​p 3.8.1d for TS140

    Recently purchased a TS140 (70A4 001RUS). Came factory installed RAID 1 with Windows Server 2012 Essentials pre-installed. Needed to reinstall, however:
    - Windows Server 2012 Essentials does not show up in EasyStartup 3.8.1c DVD that came with server
    - Downloaded latest EasyStartup 3.8.1d and created bootable DVD and ran with same result
    - "Windows Server 2012" is listed (but not Essentials). Running this installation, it does not recognize the Windows Server 2012 Essentials External Recovery DVD that came with server. Continually asks to insert "Windows Server 2012" disk.
    - "Windows Small Business Server 2011 Essentials" is listed (but not 2012 Essentials). Running this installation, it does not recognize the Windows Server 2012 Essentials External Recovery DVD that came with server. Continually asks to insert "Windows Small Business Server 2011 Essentials" disk.
    - Have booted using UEFI, Legacy and Auto with no difference
    - Ran lastest Firmware Updater v1.8.1013 - no updates listed as required
    - Have updated BIOS to latest 70A
    - Server will also not boot directly from Windows Server 2012 Essentials External Recovery DVD (dvd is set 1st in boot order in bios)
    - Windows Server 2012 Essentials External Recovery DVD is readable on other machines - can copy to bootable USB key and run regular Windows installation on server (this is current workaround)
    - using the above workaround, drivers must be installed manually.
    - EasyStartup 3.8.1d Readme specificly lists Windows Server 2012 Essentials as supported on the TS140 in UEFI and Legacy mode here
    As mentioned, the above workaround can work. However, this server may not always be maintained by myself and I would prefer the supplied software to acutally work properly for ease of use by others in the future.

    I have several TS140s running WSE 2012 R2.  Like you said, the easystart does not recognize properly the WSE R2 os, so I just did the basic from disc or USB install after I configured the boot drives or RAID1 array.
    The main reason to load the easy start is for drivers, however WSE found and recognized all the hardware in the unit.

  • Ipad2 shut off after down the battery but when connect the charger my ipad2 is not storing the power in the battery and i also not finding the error code ???

    ipad2 shut off after down the battery but when i connect the charger with my ipad2,  its not storing the power in the battery and i also not finding the error code ???

    If you drained the battery, it may take a bit for it to come back. I'd plug it in and leave it for a few hours and see if it's charging.
    If not, you can try to do a reset. Hold down the sleep and home keys for about 20 seconds. When you see the white apple, let go and let it reset and see if it charges.
    It's also possible that your battery has reached the end of its life. THey can only handle a finite amount of recharge cycles. If you can't get it to hold a charge, then make an appointment at your local apple store and explore your other options.

  • Wyse Thin client not connecting to Windows 2008 R2 server

    Configuration
    SBS 2011 Server 
    Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
    WYSE WT3125SE thin clients with Windows CE 5
    I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client.   Then I installed the License Manger and applied my Open license using User Cals.  Was able to login.  Next day I get the following
    error-"Because of a security error, the client could not connect to the remote computer.  Verify that you are logged onto the network and then try connecting again"    I still can connect fine from other machines even Windows Home Ed.  
    I remove license server and still was unable to connect.   Built a second Windows 2008 R2 server with RDS on it.  Was able to connect without issue.   Pointed it to the first RDS server license manager and have still been able to connect with
    the Thin Client.   The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger.    So my issue is with the license and so my question is what is it with the license server
    running on that server that is keeping thin client from connecting.  I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
    from domain still not able to connect.  Any help would be appreciated.

    We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
    The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
    of a security error, the client could not connect to the remote computer.  Verify that you are logged onto the network and then try connecting again"
    After reading all of the postings about this issue and tried the reactivate solution of the license server,
    I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
    What I did, I installed a new license server activate it but did not install licenses on it.
    I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
               HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
    Certificate
    X509 Certificate
    X509 Certificate ID
    X509 Certificate2
    Then reboot.
    After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
    reboot and all worked fine.
    So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
    that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
    x509 certs so it keeps working.
    I hope this helps someone
    This issue was driving me crazy so very happy that it is resolved now
    Cheers Frits

  • Problem: Failed to open the connection. Error Code 0x800002F4 (-2147482892)

    Problem: Failed to open the connection. Error Code 0x800002F4 (-2147482892)
    This is on two (2) separate machines. These are NEW INSTALLATION development work stations (laptops). One is Vista (Visual Studio 2008 / Crystal Reports 2008), and the other is Windows XP Pro (Visual Studio 2003 / Crystal Reports XI R1).
    I am using EXISTING CODE (established over several years), and EXISTING REPORTS (established over several years). Old development station was XP Pro, as above, and still exists, and still works fine.
    I can open the report in Crystal, and see the results just fine. Data for the report is obtained via ODBC.
    Can someone identity the actual error by the Error Code above, and advise. Thanks You in Advance.

    Ok, so let's start at step 1:
    SP 1 just released and I'd recommend applying that. The SO is available from here:
    https://smpdl.sap-ag.de/~sapidp/012002523100010503722008E/cr2008_sp1.exe
    For future reference, msm matching the above SP is here:
    https://smpdl.sap-ag.de/~sapidp/012002523100011715292008E/cr121_mm.zip
    and msi is here:
    https://smpdl.sap-ag.de/~sapidp/012002523100011722132008E/cr121_redist_install.zip
    Step 2: a few questions:
    a) I am not sure what CR SDK you are using; RDC, .NET? I suspect that you are using the CR assemblies for .NET, but do confirm.
    b) what is the database you are connecting to?
    c) is this a web or a win app?
    Step 3:  As the error can mean any number of things (to me it's just means something went wrong during the attempt to connect to the database...), the solution may vary, however the troubleshooting steps remain quite consistent:
    1) Do make sure the report is indeed working in the CR 2008 designer (e.g.; make sure "saved data" is not enabled.
    2) Try a simple new windows app with one of your reports. See if you have a report with no subreports and use it
    3) If that works, use a report with subreports
    4) If the above does not work in (1) above, create a new report to the same ODBC connection, do not code any database connection - let the report prompt for the logon parameter (PWD)
    5) Run the new report in your new app, enter the PWD when prompted
    6) If this works, add your database logon code
    7) If that works, add your original report (again, preferably with no subreports)
    8) If that fails, ensure that the subreport and main report use the same database connection type (ODBC)
    9) If it works, see if you can determine the difference between your old app and the new app.
    Ludek

  • OTP 2FA Problems with DA 2012 R2 and Windows 8.1 Client - Not prompting or OTP Code

    Hi 
    Just seeing if anyone has come across the same issue with their WIn 8.1 clients not prompting for 2FA once configured with DirectAccess 2012 R2?
    I have created the 2x OTP certificates, enabled OTP via PowerShell and set up the RADIUS server but whatever happens the Win 8.1 client does not get prompted for 2FA - They connect seamlessly?
    I have also configured the DAProbeUser on the RADIUS server
    Any help appreciated
    Thanks

    I was afraid that you'll said that
    I hate to be the annoying guy but take a look at this KB article:
    http://support.microsoft.com/kb/2787534
    Applied to: Windows 8\2012,
    Doesn't Apply to: Windows 8.1\2012 R2
    and - for a fact, doesn't include in Windows 8.1\2012 R2 as this bug still exists in those operating systems.
    another annoying fact - No other update was released for these version yet.
    this example approves that not every hotfix \ updates that was released for 8\2012 before 8.1\2012 R2, is already included in 8.1\2012 R2
    and allow me to add another fact.
    when you configure DirectAccess via the remote access wizard it creates a WMI query called
    DirectAccess - Laptop Only WMI Filter.
    after you create it in Windows Server 2012 R2 - look at the WMI Query and you'll see that by default it doesn't apply to version 6.3! the version for Windows 8.1.
    if you want to add the support for Windows 8.1 you have to modify manually the query which is of course, not supported by Microsoft.
    That is just another symptom that makes me wonder if Microsoft did ANY change or update to DirectAccess 2012 R2
    Tamir Levy

  • Adobe Creative Cloud CC Update is not being installed - error code 50

    Hi,
    I'm trying to update my Adobe Creative cloud client to the current version
    At exactly 50% the installation stops and the message "Creative cloud could not be updated, error code 50" appears.
    What can I do?

    The above solution should work ,
    However , if still face issue ,
    Try below steps  (Windows)
    1) Uninstall Adobe Creative Cloud  from Control panel.
    2)Open C:drive and navigate to C:\Program Files (x86)\Common Files\Adobe.
    Open Adobe folder and delete folders named Adobe Application Manager and OOBE.
    3)
    Navigate to C:\Program Files (x86)\Adobe.
    Open Adobe folder and if present delete Adobe Creative Cloud folder.
    4)
    Press Windows button (located between Ctrl and Alt buttons) along with R button together at a time , you will get a run command window.
    Type in below command and hit 'Enter' key.
    appdata
    Then navigate to Local>Adobe.
    Open Adobe folder and delete folders named AAMUpdater and OOBE.
    5)Run the Adobe Cleaner tool , if present remove Creative Cloud Desktop or Adobe Application manager.
    https://helpx.adobe.com/content/help/en/creative-suite/kb/cs5-cleaner-tool-installation-pr oblems/_jcr_content/main-pars/…
    6)
    Click on the below link and download Creative Cloud setup and then right click on it and select " Run as Administrator" .
    https://creative.adobe.com/products/creative-cloud

Maybe you are looking for