Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


issue(s) with windows 10 anniversary update

  • Please log in to reply
No replies to this topic

#1 Myekat


  • Members
  • 1 posts
  • Local time:03:31 AM

Posted 31 December 2016 - 05:34 PM

Hello all,


I updated to Windows 10 from  8.1 12/2015.  I didn't notice any problems.  In October 2016, Windows auto update downloaded the update to my pc (notebook), but there were errors in the install--probably due to lack of disk space.  I have messed with it on & off since that time.  I downloaded the media creator tool onto a usb drive to install.  The installation moved along ok until it checked the notebook for space.  It came up that i needed more disk space and either to make some space of select an external drive.  I had 2 usb drives available.  One drive had 28 GB space and the other 98.  The installation would not respond after selecting either drive and I could not move forward.  I am trying to decide if I should downgrade or what to do exactly.


While trying to figure that issue out; somehow I stumbled upon the event viewer and found that there are numerous errors and warnings that have been being logged.  They go back to 12/2015.  I have not noticed this causing problems, but would still like it fixed.  Attached is a clip of the event viewer.


I need advice and help to proceed from here.  I greatly appreciate ANY information. 


PS - I had also seen postings regarding command error.  I think that's what it was.  Anyway, it said to sfc /  scannow.  I ran that and it shows that there are corrupt files that it cannot fix.  I have attached a pdf of the cbs log.


Thanks in advance!

Attached Files

Edited by Myekat, 31 December 2016 - 05:48 PM.

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users