Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Software Troubleshooting
Rare service after windows 10 anniversary update
Message
<blockquote data-quote="SpartacusSystem" data-source="post: 532132" data-attributes="member: 39430"><p>Deleted all accounts except my own. Performed an sfc/scannow, showed there was errors in the cbs log but they couldn't be fixed. Then I used my fresh Windows 10 Pro ISO DVD to perform a DISM repair which was successful. I restarted the computer and then performed an sfc /scannow the errors found were fixed! So I restarted the computer (at this point in time i was running around the front room thinking I might have just pulled it off!).</p><p></p><p>Tried to create a new local account entitled 'Visitor'. Went over to lusermgr.msc to affix it to the Guests' group. I actually got logged into the account so I made some progress compared to before where it was pretending to sign me in then out. I was defeated by that horrible blue box which says there was a problem and we couldn't sign you into your account.</p><p></p><p>I dismissed the message and yet it behaves like a normal guest account just like in build 10586? I can save items, log out and they're still there upon restart of the laptop. Everytime I log into that account it seems to keep showing me that blue box and all I do is dismiss it.</p><p></p><p>I have some more options to perform. Make a local account and leave it in the users group and see how it works; make a local account and assign it to the administrator's group and if it's successful (I don't see a blue box) then see how it behaves when I will re-assign it to the guests' group.</p><p></p><p>The blue box message could just be a bug?</p><p></p><p>I performed a computer repair job today. I did a clean Install of Windows 10 yet those wierd services are still present. I made a guest account on that freshly installed OS and guess what? The dreaded blue box had came back to haunt me once again.</p><p></p><p>P.S. on a good note: Remember how the DISM tool used to be stuck for AGES on 20%? Well... That's not the case anymore! It actually progresses through from 0.0 to 100.0 (I have screenshots for proof which I will upload in this post the minute I transfer over to the other machine.) <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite116" alt=":D" title="Big grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>I have persistence! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite110" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> I will not be defeated by the dreaded "clean install".</p><p></p><p>Still yet to update when I'm out of juice.</p></blockquote><p></p>
[QUOTE="SpartacusSystem, post: 532132, member: 39430"] Deleted all accounts except my own. Performed an sfc/scannow, showed there was errors in the cbs log but they couldn't be fixed. Then I used my fresh Windows 10 Pro ISO DVD to perform a DISM repair which was successful. I restarted the computer and then performed an sfc /scannow the errors found were fixed! So I restarted the computer (at this point in time i was running around the front room thinking I might have just pulled it off!). Tried to create a new local account entitled 'Visitor'. Went over to lusermgr.msc to affix it to the Guests' group. I actually got logged into the account so I made some progress compared to before where it was pretending to sign me in then out. I was defeated by that horrible blue box which says there was a problem and we couldn't sign you into your account. I dismissed the message and yet it behaves like a normal guest account just like in build 10586? I can save items, log out and they're still there upon restart of the laptop. Everytime I log into that account it seems to keep showing me that blue box and all I do is dismiss it. I have some more options to perform. Make a local account and leave it in the users group and see how it works; make a local account and assign it to the administrator's group and if it's successful (I don't see a blue box) then see how it behaves when I will re-assign it to the guests' group. The blue box message could just be a bug? I performed a computer repair job today. I did a clean Install of Windows 10 yet those wierd services are still present. I made a guest account on that freshly installed OS and guess what? The dreaded blue box had came back to haunt me once again. P.S. on a good note: Remember how the DISM tool used to be stuck for AGES on 20%? Well... That's not the case anymore! It actually progresses through from 0.0 to 100.0 (I have screenshots for proof which I will upload in this post the minute I transfer over to the other machine.) :D I have persistence! ;) I will not be defeated by the dreaded "clean install". Still yet to update when I'm out of juice. [/QUOTE]
Insert quotes…
Verification
Post reply
Top