Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Taskbar frozen completely (Resolved).

- - - - -

Best Answer phillpower2 , 20 July 2016 - 08:03 AM

The ISO that was used for the upgrade should be fine as one of the restrictions with the ISO will have been that it must first be used to upgrade the original OS and only after that should it be us... Go to the full post »


  • Please log in to reply

#1
The_Shadow_630

The_Shadow_630

    Member

  • Member
  • PipPipPip
  • 161 posts

So, I came to my desktop today only to find that it had restarted, not all that odd with the frequent release of Windows updates.  We had also had a thunderstorm the night before so there is the possibility of a power flash as well.

 

At first glance however, it looked like it had booted as it should have and everything was fine.  Then I sat down and noticed there was a notification in the action center, so I went to clear it and the action center would not come up at all.  I thought this was odd, but figured maybe something was hanging so I would just restart the computer, or at least log out and back in again.  I clicked the start menu, and it would not come up either.  The Search bar is also non-functional.  I quickly came to realize that everything on the taskbar was completely non-functional.  However, if I open a file from the desktop, it opens just fine.  Everything seems to be working with exception of the taskbar itself.

 

So to Google I go to find some potential answers.  As I to some degree expected, I was instructed to run "sfc /scannow".  I did that, and it came back saying there were some corrupt files it could not repair and gave me the location of the report as per usual.  I was also instructed to run "Dism /Online /Cleanup-Image /RestoreHealth" which ran to completion without issue.  I restarted the computer with hopes the issue would be resolved, but alas, it was not.

 

I checked on recently installed updates, the only one that was there was an Adobe update that installed days ago and the computer has been fine since then.  I have attached the CBS log file for reference should it be of assistance.

Attached Files

  • Attached File  CBS.log   3MB   194 downloads

  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,364 posts

Hello The_Shadow_630

 

You do not mention it in your OP so need to ask, have you tried a system restore point that is before the time and date that this first happened.

 

From your CBS log we can see multiple instances of the following;

 

 000012e9 Error - Overlap: Duplicate ownership for directory [l:29]"\??\C:\WINDOWS\System32\lt-LT" in component Microsoft-Windows-comdlg32.Resources, version 10.0.10586.0, arch amd64, culture [l:5]"lt-lt", nonSxS, pkt {l:8 b:31bf3856ad364e35}

 

 

From your OP;

 

As I to some degree expected, I was instructed to run "sfc /scannow".  I did that, and it came back saying there were some corrupt files it could not repair and gave me the location of the report as per usual.  I was also instructed to run "Dism /Online /Cleanup-Image /RestoreHealth" 

 

 

When Windows is so badly corrupted before SFC has any chance of repairing the OS you need to run Dism /Online /Cleanup-Image /RestoreHealth first, then SFC and in some instances SFC needs to be run 4 or 5 times before all repairs are completed, if this does not correct things then you are looking at 1: a system refresh. 2: a repair installation. 3: always a last resort, a fresh install.

 

Did/do you have a dism log at all,  C:\Windows\Logs\DISM\dism.log


  • 0

#3
The_Shadow_630

The_Shadow_630

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 161 posts

I did try to restore to a point before the error.  I should have mentioned it but that was one of my first steps.  The problem that arose there was that once the restore was complete, Windows would not load.  It loaded into a BSOD with error code 0xc000021ca which required a startup repair to rectify.  Startup repair completed and it booted up as it should, but with the described problem still present.

 

I have run sfc and dism a few times and the sfc report has gotten shorter each time, so here is hoping that things are getting slowly repaired with each run.  After the last run things on the taskbar have started to work but the Start menu, search bar, and action center are still non-reponsive.  The dism report is too big to attach here so I copied and pasted the entries that are time stamped for the last run yesterday.

 

2016-07-16 23:11:25, Info                  DISM   DISM Package Manager: PID=11460 TID=11464  - CDISMPackageManager::Internal_Finalize
2016-07-16 23:11:25, Info                  DISM   DISM Package Manager: PID=11460 TID=11464 <----- Ending corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize
2016-07-16 23:11:25, Info                  DISM   DISM Package Manager: PID=11460 TID=11464  - CDISMPackageManager::Internal_Finalize
2016-07-16 23:11:25, Info                  DISM   DISM Package Manager: PID=11460 TID=11464 DISM has detected a DISM component change. Requesting a shutdown. - CDISMPackageManager::Internal_Finalize
2016-07-16 23:11:25, Info                  DISM   DISM Image Session: PID=11460 TID=11464 The image session needs to be closed and re-opened before any servicing operations can be performed. - CDISMImageSession::put_ImageState
2016-07-16 23:11:25, Info                  DISM   DISM Package Manager: PID=11460 TID=11464 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Package Manager: PID=11460 TID=11464 Finalizing CBS core. - CDISMPackageManager::Finalize
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11460 TID=11464 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Manager: PID=11424 TID=4528 Closing session event handle 0x164 - CDISMManager::CloseImageSession
2016-07-16 23:11:25, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-07-16 23:11:25, Info                  DISM   DISM.EXE: 
2016-07-16 23:11:25, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2016-07-16 23:11:25, Info                  DISM   DISM.EXE: 
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11424 TID=4528 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11424 TID=4528 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2016-07-16 23:11:25, Info                  DISM   DISM Provider Store: PID=11424 TID=4528 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,364 posts

Thanks for the update  :thumbsup:

 

As things have improved slightly it may now be worth trying the following;

 

Download then run the Windows All in One Repair (free)  from here, disregard the malware guidance but follow the other steps to the letter and in particular ensuring that you first create a new restore point and perform a proper Windows clean boot before running the repair, details for the clean boot here.


  • 0

#5
The_Shadow_630

The_Shadow_630

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 161 posts

Ok, will do that tonight,  I have been able to complete the clean boot via remote, but will need to go through the steps listed while physically present at the computer for obvious reasons.  If this does not fix it, I have also created a recovery drive from another machine running the same version of Windows 10 which I planned to end up using to be able to hopefully reset Windows through or take the nuclear option of a complete reinstall, which I don't particularly want to do, especially with the gigs of games that i would have to potentially reinstall, not to mention everything else on that computer.  Will let you know how it goes this evening.


  • 0

#6
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,364 posts

:thumbsup:


  • 0

#7
The_Shadow_630

The_Shadow_630

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 161 posts

Well, process complete, and no luck.  Still have the same problem and now, with all the services shut off of course other things are being problematic.  The services piece is easy to solve, but I wonder if there are any further steps to take on the start menu, search bar, and action center before I just go to the nuclear option.

 

As a side note, I also went ahead and tried a refresh on the computer and it seems to have failed as well.  I started it and walked away and when I returned it was on the Windows loading screen (logo with circle of moving dots below it).  I decided to just let it be and let it do its thing overnight and when I returned to it this morning, it was still at the exact same place.  So I restarted it, it went through the undoing changes process and finally loaded back into the desktop, which sat as a black screen with the mouse pointer in it (which was movable).  After some time, the desktop finally loaded, but the taskbar was once again frozen and still no access to anything on it.  I think I am going to try the reset one more time with a jump drive instead of the External HDD I was using.  If it fails, not really sure if I go to complete wipe and reinstall at that point or is there is some other step to take before that.  If I go the full on nuclear option, I am kind of thinking of just reformatting the drive completely as all of my personal files are on separate physical drives in the machine and doing a clean install of Windows as hopefully that would clean up any misc junk that might be in there from the previous Win7 installation as well as the transition from 7 to 10.

 

Can a fresh and clean install be done using the downloadable Windows 10 iso that I used for the upgrade from Win10 or do I need a dedicated Win10 install or should I install Win7 again and then do the Win10 update as we are still in the free period at this time?


Edited by The_Shadow_630, 20 July 2016 - 07:16 AM.

  • 0

#8
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,364 posts
✓  Best Answer

The ISO that was used for the upgrade should be fine as one of the restrictions with the ISO will have been that it must first be used to upgrade the original OS and only after that should it be used for a clean install, this is most likely Microsofts way of confirming that you are entitled to use the ISO based on the grounds that you previously paid for a Windows 7 product key which as you know MS will detect once you install and update.


  • 0

#9
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,364 posts

Not heard back from you The_Shadow_630, do you still require assistance or is the issue now resolved, an update would be appreciated.


  • 0

#10
The_Shadow_630

The_Shadow_630

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 161 posts

Hi, sorry it has been a bit since i posted last.  So I went with the nuclear option and did a full clean install of Win10.  And by clean, I mean clean.  wiped and formatted the drive, created the partition new, and reinstalled.  After the arduous task of reinstalling things, which I am just now finishing up, everything seems to actually be working as it should, and possibly even a bit better than before the issue showed up.  Thankfully, since I have a dedicated drive just for the OS, nothing else has been lost in any way, included saved game files and installs, which is awesome.  I would love to know what caused this major corruption of files to happen so as to prevent it in the future, but I went this route as I was getting to a point where the time spent troubleshooting was becoming too much and all roads were leading to dead ends so might as well start fresh since I could do it without loss of data.  Thank you so much for all your help, and having the resources that you provided will be helpful in the future as I support others.

 

My two big lessons from this though are 1) do regular image backups and 2) if at all possible, have separate drives or at least partitions for the OS and all other files.


  • 0

#11
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,364 posts

Hello The_Shadow_630,

 

It took some time and trouble but glad to hear that all is now well and a job well done on your behalf  :thumbsup:

 

As to what caused the problem, hard to say but two possibilities come to mind, a bad update or if an upgrade from 7 to 10 a less than perfect upgrade, the former as you will be aware is quite a common occurrence when updating any OS but the latter is less common with custom builds and seems to predominantly affect brand name computers such as Dell and HP etc which I suspect is as a result of pre installed bloatware and incompatible drivers.

 

My two big lessons from this though are 1) do regular image backups and 2) if at all possible, have separate drives or at least partitions for the OS and all other files.

 

 

Sound advice and if I may also add a #3, create a back up image of your most important drives using a free software such as Macrium Reflect (free) see tutorial courtesy of Essexboy here

 

You are most welcome btw and thank you for your kind words  :)


  • 0

#12
The_Shadow_630

The_Shadow_630

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 161 posts

Yeah, my first go to as to the source of the issue was a Windows update not installing properly or messing things up, as that has happened to me before.  So I checked the update log to see what was last installed and there was no Windows update listed in the past few weeks.  I would accuse the update from 7 to 10 if it were not for the fact that this computer has been running solidly on 10 for several months now with no major issues.  My guess is one of two things.  1) program update that ran and somehow messed with something or 2) the thunderstorm that day, which caused a power surge as indicated by the 2 flipped breakers (1 of which being the one for that room) and therefore a power outage happened to hit at just the wrong time when the OS was doing something and it caused a corrupt or incomplete file in just the wrong place.  I know the second sounds like a very peculiar and unfortunate set of events, but that was me going to the point of failure and figuring out what changed between normal operation and the failure, and that power surge and outage is the only thing that I can find evidence of having changed in that timeframe.  Even the last program update was days before the failure.  I have that computer on a pretty good surge suppressor (though as I say that I am thinking that if there was a surge I might want to replace it now), but it is not a UPS so I could certainly see a sudden power outage at just the wrong time causing a problem.

 

Totally agree on the added advice.  The more that is backed up the better.  Rather have it and not need it than need it and not have it.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP