User error or more Microsoft sabotage?

Status
Not open for further replies.
rezerekted

rezerekted

2[H]4U
Joined
Apr 6, 2015
Messages
3,054
I can't boot to safe mode. I know of three ways to do it. Use boot options in msconfig (I can no no longer select them), press shift when restarting your PC and you are supposed to get boot options such as repiar, safe mode, shutdown, etc, (all it shows now is a heading of Options and the only option being shutdown), another way is press shift on boot up and again you are supposed to see a list of options including boot to safe mode (all it get now is nothing at all and it continues to login screen).

This is on Win8.1 and not Win10 so wtf is going on? Maybe I changed an option in gpedit? I'm going with Microsoft sabotage taking away user control even further right now.

p.s. yes I ran msconfig with admin rights
 
You admit you probably altered the Windows defaults by making a Group Policy Edit - YOU changed something (and from reading previous posts it's pretty obvious that you have made quite a few changes on your machine) - and yet it's Microsoft that now gets your blame? Again? Really?

By the way: when are you switching to Linux 'cause you've pretty much railed against Windows for a long time, Linux could use some of that energy you're putting into all that ranting. ;)
 
Last edited by a moderator:
Since when are gpedit changes even required in a normal windows setting? Sometimes I wonder..
 
Here is what I have tried so far. Booted to Win8.1 install media and did a repair boot config, that gave me back being able to select safemode in msconfig so selected safe mode and rebooted, no safe mode, it is same as regular mode. Ran a Windows repair tool that has option to repair any issues with safemode. That gave me the continue option besides just shutdown when pressing shift while restarting the PC but still no safemode.

There are lots of things I might use gpedit for, such as when access is denied I have it set to give a "fuck off" error message. :)

I just went through gpedit and see nothing that would disable safe mode and none of the changes I have made should cause that to happen.

I use secpol too to do things like rename accounts and disable guest account, etc. so don't tell me to leave things alone.

Just ran a tool that reset al permisisons to default on files and registry entries, sfc and dmi, ran mcert and Microsoft security baseline analyzer, still no safemode.

Is there a service I may have monkeyed with that could have caused it?

Checked gpedit and secpol and see nothing I changed that would remove access to safemode. If it wasn't Microsoft that did it then what did? When's the last time you rebooted to safe mode? Go try it now and tell me what happens.
 
Last edited:
I rebooted to Safe Mode with F8, chose Safe Mode (first option, no need for networking, no need for the Command Prompt), booted into Safe Mode, had a look around, rebooted back to normal operation.

What's the problem? Oh, for the record that was Windows 7. I can reboot to OSX as well if you want but safe mode under OSX is a wee bit different and strictly console mode operation.

You're running Windows, so as far as you're concerned every time there's a problem it absolutely must be Microsoft's fault even in spite of you admitting again that you've altered the system with Group Policy edits and who knows what the hell else you've done over time.

I offered you the "leave it alone" advice recently and you blew me off several times because of it and called me a hypocrite but think about your current situation: you have modified your Windows installation and now you're having trouble for whatever reason that might actually be the cause of the trouble and yet your basic gut level reaction is "Dammit Microsoft, why do you keep fucking up my system?" or words to that effect.

I mean really. My updated advice:

Give it a good clean install and leave it alone, and good luck with whatever your incessant modifications bring you. ;)
 
F8 does not work on Win8.1, yea, Microsoft sabotaged it. I even know the command to make F8 functional in Win8 but it does not work on Win8.1.

You are victim blaming, it might be some software I installed that has caused it, or maybe I am right all along and Microsoft has sabotaged it, you are running Win7 and not Win8.1 so wtf do you know?

BTW, my PC is dual boot Linux/Windows so, yea, I do run Linux. Not going to reinstall either because my PC is running perfectly fine beside not having safe mode available for some inexplicable reason. Don't really need it anyway and would never have noticed if it wasn't for a tool I was going to test out suggested running it in safe mode with networking.

This is really going to annoy you. I enable the hidden admin account and then password protect it, I then set the default account to limited account so only way to do admin things on my PC is if you know the password, just like Linux. Yep, I'm a tweaker alright, the people Microsoft hate and is why you will never see me with Win10.
 
Victim blaming...

Jesus fucking Christ, I just read that. Actually read that. About a Windows install the OP readily admits to fucking with, extensively.

You broke it, OP. Not Microsoft. Not Obama. Not space aliens. You, dicking around with things you clearly don't understand. Just you.

I hope to god you were drunk when you posted this.
 
Tiberian said:
Protip: Windows doesn't have a true Administrator account anymore, that disappeared when Vista was released but you keep right on tweakin', tweaker. ;)
Click to expand...

Protip: this command enables it again. :)

Net user administrator /active:yes

Fuck you guys, I've been through every setting in gpedit and secpol and nothing I changed would have caused this issue. But I did make some more changes while there and now to get admin access from my limited user account you have to press ctrl+alt+del first and then the password. I made sure to to enable the options for Microsoft being blocked from installing Win10 too. LOL

I've been rocking this build since 2013 so don't make me out to be some incompetent PC user. That is real victim blaming. There is a possibility a tweak tool I ran recently caused it so am still investigating. Maybe I should install Win10 to fix it?

Correction; I've been running this build since before Battelfield 3 came out and that came out in 2011. Yea, at least five years without having to reinstall and you are going to try and denigrate me as a noob, fuck off with that.
 
Last edited:
This guy again? The one using articles written for Win2K to change virtual memory settings? Ill give you props though, you aren't afraid to get in there and hose it all up. Fixing it is how you learn things. :)

Just dont blame MS.
 
Microsot removed F8 key from accessing safemode in 8.1 update so of course I should suspect Microsoft, it is only logic to do so.

I know the command to re-enable it but it does shit. Apparently, Windows boots so fast now that it bypasses function keys. So what did we gain by having fast boot? A few seconds quicker loading and loss of function keys. Not a good trade off, IMO.

I know how to program, "Hello World" in Python so don't mess with me.
 
Last edited:
rezerekted said:
So what did we gain by having fast boot?
Click to expand...

What is this "we" shit you're going on about? I don't have issues with Windows, but some people around here apparently just can't use it without breaking it from the defaults. No offense (well honestly I don't give a rat's ass to be honest) you apparently just can't use the OS as designed so, the next time you feel like you have to ask for some assistance around here note that you have an alarming incessant tendency to call people names, reject the advice/suggestions when given, complain that no matter what you do it's Microsoft's fault, and then tell any/all of us to fuck off afterward.

I'll say it again one last time: you are not doing anything to help your case, period.
 
You can all stfu now because I have already fixed the issue. Reinstall? Never.

Something went and changed the boot flag to c: when it should be the hidden system partition. I used gparted to change the boot flag back to the correct partition and now I have safemode back. Thanks for trying to help with your thoughtful ideas though. /s

And, yes, Tibs, you are very arrogant.
 
Guys C'mon. Guys.

He admitted he'd messed with it.
He's open about it being sabotage, which is always an option - see malware.
Also, maybe it's just me but I literally love messing with operating systems. Tweaker? sure. Gave me a wealth of knowledge.
Did I spend days troubleshooting network issues which arose from following Black Viper's service guides? sure. Did I learn about services? yes. Was I able to fix my own mistakes? yeah, I had a piece of paper and a pen and I wrote down what I f**ed with.
Guuuuise... C'mon... Guisee
 
michalrz said:
Guys C'mon. Guys.

He admitted he'd messed with it.
He's open about it being sabotage, which is always an option - see malware.
Also, maybe it's just me but I literally love messing with operating systems. Tweaker? sure. Gave me a wealth of knowledge.
Did I spend days troubleshooting network issues which arose from following Black Viper's service guides? sure. Did I learn about services? yes. Was I able to fix my own mistakes? yeah, I had a piece of paper and a pen and I wrote down what I f**ed with.
Guuuuise... C'mon... Guisee
Click to expand...

Sure..until he said this "I'm going with Microsoft sabotage taking away user control even further right now."
Classic blame someone else for your own actions.
 
Monkey God said:
Sure..until he said this "I'm going with Microsoft sabotage taking away user control even further right now."
Classic blame someone else for your own actions.
Click to expand...

Every stereotype has an origin coming from a grain of observation.
Microsoft doing questionable things has some truth in it.
Rezerekted ranting about Microsoft does happen.
Rezerekted messing with and in consequence messing up his system - fact.
I happen to share some of his views, in that I dislike most companies and take paranoia into account because money is involved where software is developed.
I have also on numerous times said Intel was secretly putting toothpaste under the CPU heatspreader since 22nm.
I have overclocked an Intel quad to the point the VRM section on the mobo became brownish and warped, but I don't claim Intel makes bad CPUs, Gigabyte makes bad boards or that overclocking should be frowned upon like OS tweaking.
 
Snufykat said:
User error.
Click to expand...

Yes, and no. I ran a few security scanners and one of those probably caused it. Roguekiller maybe.

Claiming I screwed it up because I monkeyed with gpedit is pure bullshit. The only reason I have 8.1 Pro is for gpedit and secpol.

I have remote assistance off because I wouldn't trust them on my PC anyway.

Shit happens but I always fix it and don't just give up and reinstall. Reinstalling at the first sign of trouble is for pussies. :)
 
My issue was more the MS blame than the gpediting. I agree I would rather fix it than reinstall but your blame was in the wrong court from the very beginning.
 
rezerekted said:
You can all stfu now because I have already fixed the issue. Reinstall? Never.

Something went and changed the boot flag to c: when it should be the hidden system partition. I used gparted to change the boot flag back to the correct partition and now I have safemode back. Thanks for trying to help with your thoughtful ideas though. /s

And, yes, Tibs, you are very arrogant.
Click to expand...

"Something" like you dicking around re-enabling things from previous versions of windows because reasons. It couldn't possibly be from you tweaking stuff that never needed to be tweaked in the first place, it had to be something else or somebody else that did it...

come on man, just admit you tweaked it, u f'd up some setting, and now you fixed it. The good part is you figured out how to fix what you messed up. Good on you for that.
 
It's not PEBKAC if a utility I ran did it. You see, both my hidden system partiton and C: are bootable from futzing around with mbr when installing Linux so something I ran saw that and changed the boot flag to the C: partition. How is that PEBKAC? Anyway, back to my tweak freedom world while you take your soma and enjoy your walled garden of Win10. LOL

p.s. If Microsoft never created that hidden system partition this would never have ever happened so they are to blame indirectly.
 
Last edited:
rezerekted said:
It's not PEBKAC if a utility I ran did it. You see, both my hidden system partiton and C: are bootable from futzing around with mbr when installing Linux so something I ran saw that and changed the boot flag to the C: partition. How is that PEBKAC? Anyway, back to my tweak freedom world while you take your soma and enjoy your walled garden of Win10. LOL

p.s. If Microsoft never created that hidden system partition this would never have ever happened so they are to blame indirectly.
Click to expand...

You choose to run that third party software that you now say may have caused the problem, but you still won't man up and take personal responsibility. Rather you again try to shift blame to Microsoft for a hidden partition that, as far as I know, is routinely created and has been for a number of years.
 
54402270.jpg
 
Yeah, back off guyez! He is totally an experienced super advanced system administrator with tons of experience because he can read The googlez and do the things with the stuffs from 3 generations ago! So obviously there is no way the thingz and the stuffz he knows could be the problem!
 
Hey let's open a whole new can of worms. It was obviously the gun. The gun was at fault, the holder wasn't responsible for anything he did with it.
 
Chuklr said:
You choose to run that third party software that you now say may have caused the problem, but you still won't man up and take personal responsibility. Rather you again try to shift blame to Microsoft for a hidden partition that, as far as I know, is routinely created and has been for a number of years.
Click to expand...

No, it hasn't. It started being created with Win8. and on my PC is a 350mb partition. I'm not talking about those other unallocated 1mb partitions it creates that seem to serve no purpose. Anyway, I'm sure all of you at some time have had a similar issue happen to you so berating me for this is just idiocy and hypocrisy.

You are like a pack of rabid hyenas coming in for the kill on a wounded rabbit. Sad.
 
rezerekted said:
No, it hasn't. It started being created with Win8. and on my PC is a 350mb partition. I'm not talking about those other unallocated 1mb partitions it creates that seem to serve no purpose. Anyway, I'm sure all of you at some time have had a similar issue happen to you so berating me for this is just idiocy and hypocrisy.
Click to expand...

Most of us have had issues like that, but we didn't try blame Microsoft or another program that put us in the situation you are in. We took ownership of the problems we put on ourselves and we learned from our mistakes instead of making ludicrous threads ranting about how Microsoft is "sabotaging" our systems.
 
Last edited:
rezerekted said:
No, it hasn't. It started being created with Win8. and on my PC is a 350mb partition. I'm not talking about those other unallocated 1mb partitions it creates that seem to serve no purpose. Anyway, I'm sure all of you at some time have had a similar issue happen to you so berating me for this is just idiocy and hypocrisy.

You are like a pack of rabid hyenas coming in for the kill on a wounded rabbit. Sad.
Click to expand...

A similar issue where we immediately jumped to conclusions that it must be an update, even though we heavily modified the system with a number of disparate utilities and old outdated configurations? And then when it was pointed out that it was probably one of those continued to blame Microsoft? And then when it was confirmed it was something else, STILL continued to blame Microsoft? No I don't believe I have done that before...

And btw, those hidden Windows partitions are use for...*drum roll* boot and recovery, like when you want to boot into safe mode... So messing with them obviously would mess with your built-in recovery options. And the reasons Windows hides it..*drum roll* so you don't accidentally overwrite it within Windows... So it sounds like you effectively you shot yourself in the foot by not knowing how it operated and then blaming Microsoft and other programs for messing it up.

The question we are all wondering and waiting for you to answer, is when are you going to fess up to messing up your own system and apologize to Microsoft and the other utilities you have been using for blaming them?
 
Last edited:
Status
Not open for further replies.
Back
Top