windows server 2016 update
i can't fix the cred oracle can't rdp error, i tried to updatebut i'm stuck failed below, i tried renaming catroot2 into .old but stil no luck any recommendations?2018-05 cumulative update for windows server 2016 for x64-based systems (kb4103723)
 2018-04 cumulative update for windows server 2016 for x64-based systems (kb4093120) 2018-05 cumulative update for windows server 2016 for x64-based systems (kb4103723)
2018-04 cumulative update for windows server 2016 for x64-based systems (kb4093120)
2018-04 cumulative update for windows server 2016 for x64-based systems (kb4093120)
 2018-04 cumulative update for windows server 2016 for x64-based systems (kb4093120)2018-05 cumulative update for windows server 2016 for x64-based systems (kb4103723)
2018-04 cumulative update for windows server 2016 for x64-based systems (kb4093120)
2018-04 cumulative update for windows server 2016 for x64-based systems (kb4093120)
hi guys do the software distribution rename to . old and catroot2 to .oldto allow recreate, restart the server, make sure the services are working bits, cryptsvc, windows installer, windows updateit worked for me
It seems that updating Windows 7 has become a task that tests our patience and is accompanied by many unforeseen events.
**If you have installed Windows 7 and you are not able to update it because Windows Update is constantly looking for updates, here you will find the solution.**




![image](https://technowikis.com/sites/technowikis.com/uploads/084/8408675506832124429.jpg)




The problem of the search for updates is accompanied by a high consumption of RAM and CPU that does not allow even a good use of the PC while looking for updates. The problem is with Windows Update and how Microsoft has implemented the updates.




Windows 7 does not update, it keeps looking for updates forever and finds nothing.




**The first thing you need to know is if you are installing Windows 7 32bit or 64bit.**
Once we have this information, we can begin the process.



 
Disable Windows Update to make the update process faster.



First
[we open a terminal with administrator permissions](https://translate.googleusercontent.com/translate_c?act=url&depth=2&hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=es&sp=nmt4&tl=en&u=https://www.vozidea.com/abrir-consola-comandos-terminal-windows&xid=17259,15700023,15700186,15700190,15700256,15700259,15700262,15700265&usg=ALkJrhhqpP0r1As5JhHykWgqvcIjB7PXng)
to
**stop the Windows Update service**
with the command:
  

`net stop wuauserv`




![image](https://technowikis.com/sites/technowikis.com/uploads/133/13323206954024179447.jpg)



 
Manually install update KB3020369.



**Installing this update is an essential requirement to solve this problem.**
It is the first step and if we do not install this update first, we will not be able to follow all the steps in this tutorial.




We know that the error is generated by a Windows Update client error, which hangs when scanning new updates. Microsoft released a patch that solves the problem, but in order to install it, it requires that we download and install the KB3020369
*"April 2015 servicing stack update" update first*
:



* KB3020369 for Windows 7
**32bit**
:
<https://www.microsoft.com/es-ES/download/details.aspx?id=46827>
* KB3020369 for Windows 7
**64bit**
:
<https://www.microsoft.com/es-ES/download/details.aspx?id=46817>



Two options to finish solving the Windows Update error in Windows 7.




At this point we have two options:



* **Download and manually install updates KB3172605 and KB3138612.**
Once installed, Windows Update should work correctly and we could update Windows 7 without problems.
* **Download and install the KB3125574 package released by Microsoft with all security updates until April 2016 and that allows you to update a Windows 7 installation faster.**
This package occupies more than 316MB in 32bit systems and 476.9MB in 64bit systems.



Both options work correctly, but it is true that
**downloading and installing the cumulative update KB3125574 is a more convenient and faster process, so it is the option I recommend for most users**
. Even so, I will explain both options.



 
Recommended option, download and install the KB3125574 package released by Microsoft with all security updates until April 2016.



![image](https://technowikis.com/sites/technowikis.com/uploads/171/17135527325084971355.jpg)




This update package can be found through the
[Microsoft Update Catalog](https://translate.googleusercontent.com/translate_c?act=url&depth=2&hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=es&sp=nmt4&tl=en&u=http://www.catalog.update.microsoft.com/Search.aspx%3Fq%3D3125574&xid=17259,15700023,15700186,15700190,15700256,15700259,15700262,15700265&usg=ALkJrhgYZAtq0r4K4ryYk_7h4_sjeQs_-A)
or you can download it directly from the following links:



* Update package for Windows 7
**32bit**
:
[windows6.1-kb3125574-v4-x86\_ba1ff5537312561795cc04db0b02fbb0a74b2cbd.msu](http://download.windowsupdate.com/d/msdownload/update/software/updt/2016/05/windows6.1-kb3125574-v4-x86_ba1ff5537312561795cc04db0b02fbb0a74b2cbd.msu)
* Update package for Windows 7
**64bit**
:
[windows6.1-kb3125574-v4-x64\_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu](http://download.windowsupdate.com/d/msdownload/update/software/updt/2016/05/windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu)



Once the system is installed and restarted, we can now run Windows Update normally that will detect the remaining updates without problems.



 
Alternative option, manually download and install updates KB3172605 and KB3138612.



Next
**we download and install the KB3172605 patch**
:



* Download for Windows 7
**32bit**
:
<https://www.microsoft.com/es-ES/download/details.aspx?id=53335>
* Download for Windows 7
**64bit**
:
<https://www.microsoft.com/es-ES/download/details.aspx?id=53332>



Finally,
**we download and install the update for the Windows Update client of March 2016 (KB3138612)**
:



* For Windows 7
**32bit**
:
<https://www.microsoft.com/en-us/download/details.aspx?id=51208>
* For Windows 7
**64bit**
:
<https://www.microsoft.com/en-us/download/details.aspx?id=51212>



**Now we restart Windows 7 and rerun Windows Update to search for all available updates.**
In my case it has been a little more than 20 minutes looking for updates until it finally allowed me to install all the updates. We currently have all our machines still on Windows XP and have only just upgraded some with Office 2007.


Budget dollars just have been too cost prohibitive to upgrade all 1,000 of our workstations. At some point due to licensing and availability we will be forced to upgrade. 


The one thing I’ve noticed difficulty with right off the bat has been the ability to connect via RDP to a Windows Server 2008 box. Without some registry hacks/mods in XP this can be problematic if the server is set to the newest (and more secure) RDP protocol. Windows 7 doesn’t have this issue. upgrade revit to 2018.3. that will fix it. thank you for taking interest in my post.

i have solved the problem.it was mistake from my own part.

i have disabled some of the hardware detection services before the update.

i have disabled the "device install service" on the windows service

[[asas]](https://aws1.discourse-cdn.com/arduino/original/4x/5/0/9/509934b6660953c4e848dc95f40efd35d02bfe60.png "asas")

renabling it and rebooting it solved the … Hi Jamey6588540,Please follow the steps mentioned in the below link to fix the paper capture service:[Could not access the recognition service when attempting OCR on Windows](https://community.adobe.com/external-link.jspa?url=https%3A%2F%2Fhelpx.adobe.com%2Facrobat%2Fkb%2Facrobat-could-access-recognition-service.html)Divya what to do::

docker exec -it gitlab /bin/bash

then

apt install update-manager-core

then

do-release-upgrade [image] t\_t:

1738508

those domains are pending name server update, [@t\_t](/u/t_t), that has to happen prior to transferring the domain to cloudflare registrar, good tip here, [community tip - fixing “pending nameserver update”](https://community.cloudflare.com/t/community-tip-fixing-pending-nameserver-update/75415) . [image] soydepr:

certbot: error: unrecognized arguments: renewal

you should still be able to renew. the command is:

certbot-auto renew we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: the problem has been solved.

i got in contact with our provider and they were able to apply the proper access to the folder for verification.

thank you for all of your help and patience. this thread can now be closed.