Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

PROCESS1_INITIALIZATION_FAILED Windows 10

  • 12-03-2016 8:20pm
    #1
    mightybashful
    Registered Users, Registered Users 2 Posts: 1,260 ✭✭✭


    I got this error on a HP Pavillion today. I've found a couple of suggested fixes but neither worked. And the Microsoft advise pages aren't worth the space they up on the internet

    Windows 10 came pre-installed so I don't have the disc.

    Do anybody how, or has anybody been able to fix this before?

    If I had hair it'd be pulled out by now :(


Comments

  • #2
    mp22
    Moderators, Business & Finance Moderators, Regional South Moderators Posts: 6,854 Mod ✭✭✭✭mp22


    According to google "disabling secure boot in the bios is a possible fix" might be worth a try


  • #3
    mightybashful
    Registered Users, Registered Users 2 Posts: 1,260 ✭✭✭mightybashful


    mp22 wrote: »
    According to google "disabling secure boot in the bios is a possible fix" might be worth a try

    Thanks. It was one of the suggested fixes I found. No joy :(


  • #4
    mightybashful
    Registered Users, Registered Users 2 Posts: 1,260 ✭✭✭mightybashful


    I ended up wiping my laptop and installing Linux on it last night after running out of patience.

    I could get as far as trouble shooting but it kept looping to a repair screen which did nothing. Was like watching a max headroom programme.

    From trawling through MS forums this seems common enough but MS have no definite fix yet.


Advertisement