| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 146024 | 2018-04-03 10:14:00 | Weird Win10 | bk T (215) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1448041 | 2018-04-04 23:53:00 | Crystal disk shows BLUE. Running Memory check with MemTest 86 How long should I run the test? High chance that it's the HDD although crystal disk shows blue. |
bk T (215) | ||
| 1448042 | 2018-04-05 00:07:00 | Crystal disk shows BLUE. Running Memory check with MemTest 86 How long should I run the test? High chance that it's the HDD although crystal disk shows blue. A memory test is not a quick test, of course if the memory is bad it generally shows up quick, but its not uncommon to leave memtest running overnight. yep the HDD can still be faulty, had drives show up as Blue, then fail the next day. All that test is doing is reading the drives SMART. What's the eventvwr logs say /show ? Heres what one with a bad Drive looks like. 8761 What you can also look at is the reliability log, Sometimes if gives answers. Click on the search, type in Reli Open View reliability History. |
wainuitech (129) | ||
| 1448043 | 2018-04-05 00:12:00 | Running Memtest now. Will check the event viewer and reliability log later. Thanks wainuitech. |
bk T (215) | ||
| 1448044 | 2018-04-05 04:52:00 | 4 hours has gone and Memtest found nothing wrong with it, so I stopped the test. Event Viewer found many lines of the following errors in red: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool." Details: 8762 Any clue? Reliability monitor shows nothing -- clean |
bk T (215) | ||
| 1448045 | 2018-04-05 05:01:00 | I had a PC with a corrupted profile that was causing weird issues - although mainly with the windows store and the Netflix app. Never did find a cure or a cause, just made a new profile and started over after a few attempts of fixing it. In any case you can just create another profile to test with, if it doesn't help you can delete it and go back and if it does you can delete the old one. |
dugimodo (138) | ||
| 1448046 | 2018-04-05 05:18:00 | This problem is very similar to the initial problem that I need to log out and login . BTW, how do I create a new profile? |
bk T (215) | ||
| 1448047 | 2018-04-05 07:13:00 | The event viewer error, "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID ...." Has it got something to do with the 'Activation' of Windows? |
bk T (215) | ||
| 1448048 | 2018-04-05 09:16:00 | Have a look in the system to check for activation. OR from the search type in Activation Open the result(s). Its a permission problem. Could be part and parcel with the other problem relating to the profile. Either the install media is bad, or there is some outside event ( hardware or some software installed) that's causing it. If it were mine I would install Windows from fresh, update and install NOTHING ELSE, see if the problem reappears. When installing windows you get to the option to add in a product key -- Are you entering one or leaving it blank. ? It should be blank since its had W10 on it previously. If the laptop is connected to the internet Via an Ethernet cable then it may not give the option as it may already pick it up on MS's servers. |
wainuitech (129) | ||
| 1448049 | 2018-04-05 10:44:00 | I did install Windows from fresh, wiped the HDD, I did not enter any product key, left it blank. Checked activation after installed that it was activated. Only thing I forgot was, the Ethernet cable (Internet) was plugged in during the installation process, couldn't remember which option did I choose for the log in. |
bk T (215) | ||
| 1448050 | 2018-04-05 20:30:00 | So I joined this thread literally just to chime in. We manage a whole bunch of windows 10 machines, a large percentage all started having this problem starting yesterday. It's intermittent like you said, it's crazy. It's happening on seemingly any versioned machine - 1507, 1703, 1709 have all had it. And since we have over a hundred machines I think we can say (based on the probability this all started yesterday) that it has nothing to do with 'hardware'. Also I don't know if it makes sense that the profile is corrupted since it DOES sign in sometimes. Thought's anybody? Where do we escalate this with windows? |
jonostilla (17608) | ||
| 1 2 3 4 | |||||