Jump to content

Alwithaprob

Members
  • Content Count

    23
  • Joined

  • Last visited

About Alwithaprob

  • Rank
    New Member
  1. Hi Maurice Naggar, I will do as you say and reference them to this topic after following their beginning steps. I just wanted to take the moment to say thank you for everything you have done and I wish you the best yourself as well. I have not lost the faith in this amazing team here. 👍
  2. Hi Maurice Naggar, Apologies for going at too fast of a pace there! Will most definitely slow down so you can perform your duties appropriately. As far as the services mentioned above all of them except the last two (The COM one and the Shell one) are already automatical and started. The last two (the two I just mentioned) say they are automatic BUT can't be started in safe mode so not sure if that will have any effect on your troubleshooting. Both scans came back clean again. See attached logs. msert.log mbamreport3.txt
  3. Yes I am currently in safe mode with networking only devices connected -mouse -keyboard -monitor -power cable -netgear network adapter
  4. I am unable to get it to load into Regular windows. It reboots after getting to the Windows 10 logo/spinning wheel part. 😨
  5. So... something slightly alarming. I can't load into regular Windows 10 anymore. It constantly reboots. Never gets to the login screen. I can get to safe mode just fine via f8.
  6. So it said it was applying fixes and the following two results appeared 1) Windows Update Componets must be repaired "not fixed" 2) Potential Windows Update Database error detected "fixed"
  7. From what I've read (via my phone ) part of my computers problem could be the DCOM as it can cause constant reboots if the graphic driver is not up to date? At least that's kind of what I gather? Just wanted to mention this in case it may be of use to you any. Still following you directly, -Al
  8. Hello, Still attempting to get the 1903 update to fully update. I want to say it finished downloading ?? But I get this error now "Something went wrong You can contact Microsoft Support for help with this error. here is the error code 0x0020036" It seems this issue becomes more and more complex and just well...strange! So I left my machine on last night while it was downloading the update via the linked software by Microsoft. I noticed though my computer kept restarting 2-3 times on it's own. A friend of mine at work today suggested I take a look at the event viewer. It appears the event viewer is getting a crazy amount of errors. (this is the event viewer in safe mode with networking ) DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}
  9. Ended up going here. The catalog didn't work for me https://www.microsoft.com/en-us/software-download/windows10 Should I use this?
  10. Okay so I was able to download all updates possible but it didn't show build 1903 as an option. I was able to go to the catalog though and find 1903 should I download it?
  11. erm... now it says Ren C:\Windows\System32\catroot2 Catroot2.old access is denied. i have just tried unblocking hidden folders again ( via the batch file in option 3 ) just in case it was a 1 time thing and it still did not fix it
  12. Hello command prompt is ran as admin and this error happens when I do Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old "Access is denied"
  13. 1st issue: This originates back to the original reason ( I think ) as to why I made the topic on here. After I updated to 3.8.3 I started to automatically go to Windows Recovery Environment a good 50% or more of the timed when I rebooted my machine. There had been absolutely zero surfing, zero additinal programs added, etc in a relative amount of time compared to malwarebytes upgrade. The recovery environment boots up quite often on restart claiming that is needs to diagnose and repair my system only to fail in doing so. 2nd issue: Well that was the whole windows update thing we are looking at now I guess 3rd issue: no idea I guess that's whatever else you was looking for I have done zero fixes on my own and have not done anything beyond what I have been instructed by you personally.
  14. The problem with Windows Recovery Environment is still persisting a good 50% of the time unfortunately.. I was worried the Farbar wasn't done as it restarted and had went to that Windows Recovery Environment once after it restarted the computer but once it was back in Windows it didn't restart the software so I assume it was over. I have had the following Window Update errors/updates 2019-07 Cumulative Update for WIndows 10 Version 1803 for x64 based systems (Kb4507435) (8) Last failed 07/19/19 - 0x800f0922 2019-06 Cumulative Update for Windows 10 Version 1803 for x64 based systems (kb4503286) Failed to install on 06/22/19 - 0x800f0922 The SFCfix said stage 1 of 6 failed on server whatever that means (when it was running) see attached file as requested I don't see the file you requested but this is what I do see from the command prompt + the directory it mentions Attempting repair . . . Stage 1 Stage 2 Stage 3 Due to the nature of your corruptions, scan times have been extended by approximately 15-20 minutes. Please be patient and allow the operation to complete. Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.17134.885 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log dism.log
  15. Ah! Here you go this is the right one Fixlog.txt
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.