D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 3, 2019 #41 One question, We have more tan 100 servers affected. I don't know why. When we will find the root cause of the problem, do I have to pass all this scripts or could we sintetize in only one? Thanks you!
One question, We have more tan 100 servers affected. I don't know why. When we will find the root cause of the problem, do I have to pass all this scripts or could we sintetize in only one? Thanks you!
D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 4, 2019 #42 Good morning, Any advance? Thank you.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 4, 2019 #43 Please do not double post if it has not been 48 hours since my reply. There will be multiple scripts. This cannot be done in one go.
Please do not double post if it has not been 48 hours since my reply. There will be multiple scripts. This cannot be done in one go.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 6, 2019 #45 Hi! As I said in the PM, I am working on it. It's difficult because I require both a specific update and a specific language. 1. Click your Start button and type cmd in the search box. Right-click on cmd from the search results and select Run as administrator. Answer Yes if the UAC prompt comes up. 2. Copy/Paste the following in to the command-prompt window and hit enter. wmic qfe list brief /format:texttablewsys > "%USERPROFILE%\desktop\hotfix.txt" 3. This will create a file on your desktop named hotfix.txt. Please attach this to your next reply.
Hi! As I said in the PM, I am working on it. It's difficult because I require both a specific update and a specific language. 1. Click your Start button and type cmd in the search box. Right-click on cmd from the search results and select Run as administrator. Answer Yes if the UAC prompt comes up. 2. Copy/Paste the following in to the command-prompt window and hit enter. wmic qfe list brief /format:texttablewsys > "%USERPROFILE%\desktop\hotfix.txt" 3. This will create a file on your desktop named hotfix.txt. Please attach this to your next reply.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 6, 2019 #46 Next. Afterwards, go ProcMon route. Attachments SFCFix.zip 1.5 KB · Views: 1
D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 11, 2019 #47 softwaremaniac said: Next. Afterwards, go ProcMon route. Click to expand... Thanks HOTFIX attached. SCFIX attached PROCMON as well https://1drv.ms/u/s!Aq72cZc6PrkpgQdsA1cyDBrXeZqd Different error now installing roles: 0x800f081f (Attached as well). Attachments hotfix.txt 4.2 KB · Views: 1 SFCFix.txt 4.7 KB · Views: 0 error_role.jpg 96.5 KB · Views: 2
softwaremaniac said: Next. Afterwards, go ProcMon route. Click to expand... Thanks HOTFIX attached. SCFIX attached PROCMON as well https://1drv.ms/u/s!Aq72cZc6PrkpgQdsA1cyDBrXeZqd Different error now installing roles: 0x800f081f (Attached as well).
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 11, 2019 #48 Hi! Since we're dealing with a new error code, please attach CBS.log after the failed attempt as well.
Hi! Since we're dealing with a new error code, please attach CBS.log after the failed attempt as well.
D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 12, 2019 #49 softwaremaniac said: Hi! Since we're dealing with a new error code, please attach CBS.log after the failed attempt as well. Click to expand... There you have. Thank you Attachments CBS.zip 68.6 KB · Views: 2
softwaremaniac said: Hi! Since we're dealing with a new error code, please attach CBS.log after the failed attempt as well. Click to expand... There you have. Thank you
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 12, 2019 #50 Thanks, but I'm afraid I'm gonna need the whole CBS folder.
D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 13, 2019 #51 https://1drv.ms/u/s!Aq72cZc6PrkpgQhzlk03Lrb-fkJI CBS Folder. Thanks.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 13, 2019 #52 FRST Registry Search 1. Click your Start button and choose Control Panel. 2. In the upper right corner ensure the View by: is set to Category. 3. Select the Programs group. 4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste KB4034658 into the Search box and click the Search Registry button. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt. You may close any remaining open windows now.
FRST Registry Search 1. Click your Start button and choose Control Panel. 2. In the upper right corner ensure the View by: is set to Category. 3. Select the Programs group. 4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway. Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. 5. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 7. Copy and paste KB4034658 into the Search box and click the Search Registry button. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt. You may close any remaining open windows now.
D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 14, 2019 #53 Here it is. Thanks. Attachments SearchReg.txt 2.6 MB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 14, 2019 #54 Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). Run FRST64 by Right-Clicking on the file and choosing Run as administrator. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Try roles with ProcMon. Attachments Fixlist.txt 2.2 MB · Views: 1
Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download attached file and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). Run FRST64 by Right-Clicking on the file and choosing Run as administrator. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Try roles with ProcMon.
D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 15, 2019 #55 Good morning You fixed it! I installed roles successfully! What a great job! Many many Thanks! Procmon: https://1drv.ms/u/s!Aq72cZc6PrkpgQlJrY50bO1dbgkQ So. Now I woulld like to know the root cause of this corruption. We have more than 100 servers affected and we need a "fast" way to fix server per server. How can we accomplish that? Wich is the cause, any Windows Update? Thank you very much for your help. Regards. Attachments Fixlog.txt 4.4 MB · Views: 1 fixed_roles.png 5 KB · Views: 2
Good morning You fixed it! I installed roles successfully! What a great job! Many many Thanks! Procmon: https://1drv.ms/u/s!Aq72cZc6PrkpgQlJrY50bO1dbgkQ So. Now I woulld like to know the root cause of this corruption. We have more than 100 servers affected and we need a "fast" way to fix server per server. How can we accomplish that? Wich is the cause, any Windows Update? Thank you very much for your help. Regards.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 15, 2019 #56 I cannot answer that without analyzing the logs, but some of the keys were missing and there were remnants of an earlier update blocking installation.
I cannot answer that without analyzing the logs, but some of the keys were missing and there were remnants of an earlier update blocking installation.
D dbernal Active member Joined Jan 31, 2019 Posts 30 Feb 18, 2019 #57 Good morning. Could it be the sysprep ? As I said we have more than 100 servers affected. Wich script do I have to execute "for testing" on other affected VM. Maybe the last one? FRST FIX? I will try and tell you the reseults. Thanks again.
Good morning. Could it be the sysprep ? As I said we have more than 100 servers affected. Wich script do I have to execute "for testing" on other affected VM. Maybe the last one? FRST FIX? I will try and tell you the reseults. Thanks again.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 18, 2019 #58 No, it's not Sysprep. It's a language pack issue. Do not run the fix as this was customized to the first machine only!
No, it's not Sysprep. It's a language pack issue. Do not run the fix as this was customized to the first machine only!