[SOLVED] windows 10 apps and functions not working

R

raffaele

Well-known member
Joined
Jun 21, 2018
Posts
57
Hi All
having issues with windows 10 version 1803 build 17134.112

Start button no response
No cortina
store on task bar wont work (class not registered)
Microsoft edge (class not registered)
right click on desktop display settings or personalize wont work (error "this file does not have an app associated with it")

I have tried
control panel > programs > default programs
set your default programs
when selected nothing happens

Also tried

Ctrl Alt Del
task manager
run new task (admin selected)
powershell

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

lots of red
object not found errors
cant find path errors
deployment failed with HRESULT the package could not be installed because a higher version of this package is already installed

tried DSM all good no errors
tried SFC all good no errors
tried Chkdsk


Ive googled to no avail

Any help on this would be much appreciated
 
yes I agree
I tried this
in CMD
regsvr32 ExplorerFrame.dll

error window
The module "ExplorerFrame.dll was loaded but the entry-point DllRegisterServer was not found
make sure that ExplorerFrame.dll is a valid DLL or OCX file
???
no idea beyond me
Just tried this as well
run services.msc
tried to find Internet Explorer ETW Collector Service to start but its not listed
???
My Knowledge of how windows works is limited
any help thanks in advance
I gonna backup my registry probably a good thing while its just running
 
Is it worth cloning the drive on a new one ?
Power supply ?

Prefetch seems to be running pretty hard ?
 
OK Ive run it
and
waiting for tasks to complete
is scrolling down the screen
20 + times continuing and wont stop
40 times
and still going
looks like the tasks will not complete
just saw auto start and reboot, Ill reboot and see what happens
 
Just wanted to suggest to reboot and try again :smile9:
 
Man
I must be scratching a lot of heads

Softwaremaniac helped me heaps in getting Dcom working after endless posts

Now who is the lucky one to take the rein and sort this one out
 
OK reboot, Clean boot
tried again
and got results

Code: 
We're all done! You should find the output already zipped to SysnativeFileCollectionApp.zip under C:\Users\raffaele\Documents.

Here's how to attach this file to your post:
 -  If using Quick Reply, click the Go Advanced button under the Reply box.
 -  Click the Paperclip at the top of the editor window, or scroll down and
    click the Manage Attachments button in the Additional Options section.
    You may have to expand the Additional Options section.
 -  Click the Browse... button and browse to your zipped file.
 -  Click the Upload button.
 -  Repeat for any more files, then close the Manage Attachments window.


* * *    B S O D    F I L E    C O L L E C T I O N    S C R I P T    * * *
         Authors:
            jcgriff2 - J. C. Griffith, Microsoft MVP
            TheOutcaste - Jerry Wines, Microsoft MVP
            Patrick - Patrick Barker, Microsoft MVP
            niemiro - Richard
            Tekno Venus - Stephen
         ©  https://www.sysnative.com/
         ©  sysnative.com - MVP
         © 2008 - 2014 sysnative.com
            Last Update: July 2014
         New Jersey, USA; Oregon, USA; New York, USA
         ALL RIGHTS RESERVED

 * * *   G O O D  B Y E . . .  jcgriff2
 * * *   G O O D  B Y E . . .  jcgriff2
View attachment SysnativeFileCollectionApp.zip



BTW installed new PSU
just in case the old PSU caps drying out causing noise or varying voltage rails
 
If it is stuck on msinfo32, just cancel it and upload what has been created.
 
Please make sure there's no piracy on your system.
Code: 
127.0.0.1                   activate.adobe.com
127.0.0.1                   practivate.adobe.com
127.0.0.1                   lmlicenses.wip4.adobe.com
127.0.0.1                   lm.licenses.adobe.com

Seeing the amount of chkdsk logs in your WU topic, which repeatedly reported issues, you might have a failing drive. I know the SMART was already checked, but software can do only so much and there's no way to detect all issues.
The amount of events in your eventlog related to drive / filesystem issues is also high. A few of them:
Code: 
2018-07-07T17:01:55.479        The following file necessary for Windows startup was corrupt: e:\boot\resources\custom\bootres.dll
2018-07-04T20:33:39.694        Cannot zero sectors on disk \\?\PhysicalDrive5. Error code: 5@0101000F
2018-07-04T17:30:55.095        The following file necessary for Windows startup was corrupt: d:\boot\resources\custom\bootres.dll
2018-07-03T19:08:33.724        The event logging service encountered a corrupt log file for channel Microsoft-Windows-PushNotification-Platform/Operational. The log was renamed with a .corrupt extension.
2018-07-03T19:08:27.284        The following file necessary for Windows startup was corrupt: d:\boot\resources\custom\bootres.dll
2018-07-03T18:42:23.734        A corruption was discovered in the file system structure on volume C:.
2018-07-03T18:42:20.722        A corruption was discovered in the file system structure on volume C:.
2018-07-03T18:42:17.227        A corruption was discovered in the file system structure on volume C:.
2018-07-03T18:42:05.565        A corruption was discovered in the file system structure on volume C:.
2018-07-03T18:41:29.015        A corruption was discovered in the file system structure on volume C:.
2018-07-03T18:41:19.130        A corruption was discovered in the file system structure on volume C:.
2018-07-03T18:41:07.139        A corruption was discovered in the file system structure on volume C:.
2018-07-03T18:40:56.128        Volume C: (\Device\HarddiskVolume2) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
2018-07-03T18:40:56.128        A corruption was discovered in the file system structure on volume C:.
2018-07-01T07:38:41.937        The device, \Device\Harddisk1\DR1, is not ready for access yet.
2018-06-30T08:38:30.092        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-30T08:38:29.936        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:11:11.200        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:11:11.185        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:11:11.185        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:11:11.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:41.372        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:40.935        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.060        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.013        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.013        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:10:28.013        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:09:18.232        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:09:18.232        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:09:18.013        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:09:18.013        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:58.263        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:46.638        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:44.294        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:44.232        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:44.216        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:44.216        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:44.216        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:44.216        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:44.216        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:38.857        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:25.341        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:25.341        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:15.623        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:15.607        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:15.216        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:12.685        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:07:11.716        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:06:57.888        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:06:56.810        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:06:42.810        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:51.763        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:49.591        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:48.732        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:47.013        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:47.013        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:44.326        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:44.310        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:44.248        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:44.232        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:44.232        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-23T08:05:43.967        The transaction resource manager on volume C: encountered an error during recovery.  The resource manager will continue recovery.
2018-06-18T15:41:59.708        The device, \Device\Harddisk4\DR4, is not ready for access yet.
2018-06-17T15:02:12.743        An error was detected on device \Device\Harddisk5\DR7 during a paging operation.
2018-06-17T15:02:12.743        An error was detected on device \Device\Harddisk5\DR7 during a paging operation.
2018-06-17T15:02:12.743        An error was detected on device \Device\Harddisk5\DR7 during a paging operation.
2018-06-17T15:02:12.743        An error was detected on device \Device\Harddisk5\DR7 during a paging operation.
2018-06-16T05:02:54.263        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:49:28.913        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:45:34.037        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:44:18.466        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:42:37.415        Volume C: (\Device\HarddiskVolume2) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.
2018-06-16T02:40:59.817        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:40:59.817        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:40:59.743        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:40:59.659        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:29:08.973        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:29:08.071        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:29:07.839        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:20:03.685        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:20:03.588        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:19:56.437        A corruption was discovered in the file system structure on volume C:.
2018-06-16T02:18:47.821        A corruption was discovered in the file system structure on volume C:.
2018-06-15T02:51:37.154        A corruption was discovered in the file system structure on volume C:.
2018-06-14T19:15:34.655        A corruption was discovered in the file system structure on volume C:.
2018-06-14T19:15:30.405        A corruption was discovered in the file system structure on volume C:.
2018-06-14T14:20:36.100        A corruption was discovered in the file system structure on volume C:.
2018-06-14T12:33:10.640        A corruption was discovered in the file system structure on volume C:.
2018-06-14T12:33:10.640        A corruption was discovered in the file system structure on volume C:.
2018-06-14T12:33:10.640        A corruption was discovered in the file system structure on volume C:.
2018-06-14T12:33:10.639        A corruption was discovered in the file system structure on volume C:.
2018-06-14T12:33:10.639        A corruption was discovered in the file system structure on volume C:.
2018-06-14T12:33:10.639        A corruption was discovered in the file system structure on volume C:.
2018-06-14T12:33:10.638        A corruption was discovered in the file system structure on volume C:.
2018-06-14T02:35:19.237        A corruption was discovered in the file system structure on volume C:.
2018-06-14T02:35:19.237        A corruption was discovered in the file system structure on volume C:.
2018-06-14T02:35:19.237        A corruption was discovered in the file system structure on volume C:.
2018-06-14T02:35:19.227        A corruption was discovered in the file system structure on volume C:.
 
Cool
So the fix you suggest is to try a new hard drive and remove adobe package
Ill do that later today and get back to to

Thanks Heaps
 
Thanks Axe0
I did a disk clean up first
then cloned C drive with EaseUS Todo to a brand new WD Black 2TB and new SATA lead to motherboard
Replace PSU with brand new thermaltake 750W
boot to windows no problem
Still have issues as first post
 
Cloning everything from a bad drive to a good drive doesn't solve the problem, because you copy the problems too.
I'd suggest to run a chkdsk once more and a repair install, but the latter is up to you. Although SFC is clean, it doesn't mean other Windows files aren't corrupted.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top