- This topic has 9 replies, 3 voices, and was last updated 15 years, 4 months ago by
.
-
Posts
-
Just noticed, I cannot log into Safe Mode.
I have an N220 running Windows 7, and its updated via MS-update and Samsung Update.
Whilst it boots OK into normal use, I cannot enter Safe Mode, which obviously one day I may need too,
As the PC starts, I press F8 and get the boot choice menu. I pick any of the three ‘safe modes’ (with network, command prompt or just safe mode) and I get to the log on screen showing my three accounts.
If I pick either of the user accounts or even the admin account, it prompts for the password. when I enter that, for a brief moment I see some text that appears to say “wrong user name or password” (or similar) and then almost straight away the PC restarts and the PC reboots back to a log in screen.
If I log into normal W7 on any of the accounts, all works OK.
Any ideas?
Thanks
PS – It may have always been like this from day one. Ive had the netbook for about 2 weeks now, but I cant say Ive tried safe mode access before.
what happens if you make a fresh accout w/o a password, then run safe mode and use that newly made account.
Thanks for the suggestion.
From a post on another forum, I tried creating a new password free account and tried that. It was the same, I could use it in ‘real’ W7 but not in safemode.
It gets to the safe mode log on screen, and then when I click the icon the PC restarts. Once it restarted after I just waited at the SM logon screen for a while.
Most strange, works fine for normal W7.
I can confirm, it just restarts if I wait long enough (5-7 secs) at the safe mode login menu, by itself, without me entering anything at all.
Any ideas anyone?
I assume other N220 can use safe mode.I dont know if any N220 owners could confirm this please, but Ive just contacted Samsung support on the phone, and after testing their N220, they say that these netbooks cannot use safe mode?
Apparently, their model did the same thing. Boot it up, press pick a safe mode option, let it boot to the logon menu, and wait. After a few seconds the PC reboots. Attempting to logon to safe mode also fails and restarts.
They claim its correct! (Sadly, I dont have a 2nd N220 to test it on).
Basically, they say Safe mode isn’t needed, and use the restore functionality as a fall back if Windows will not boot.
Most strange, seems odd to me. Never heard of that before.
Can anyone confirm please.
I have never heard such a thing before.
You might try method 2 here
tonytb, (thanks for the suggestion)
Neither have I.
I believe Samsung support are “less than par” shall we say.
My friends, girlfriends N220 (I have since found out) boots OK into safe mode, so clearly the model can.
Why Samsung support told me it wouldn’t, I do not know and am yet to find out.
I am reluctant to try your ‘method 2’ as I guess if it fails it may lead to cyclic restarts. However, as Samsung have basically told me to and restore, I may have nothing to lose.
I’m in touch with Samsung support via email and they seem to be back-tracking and have suggested I do an complete restore to start from the day 1 build. However, they have offered no response as to why I was told their test model behaved the same and to what they did to resolve the problem on their test model.
On the phone they told me their test model also restarted in safe mode and that this was correct for the model. I thought this was unlikely to say the least and therefore emailed them. Which is why I also asked on the forum if anyone on the forum had an N220 that could safe mode boot. Their (Samsung support) first email response seems to suggest that the phone information I was given was nonsense.
I may be wrong, but I think Samsung (the manufacturer) may make a good netbook PC, but their support team are, shall we say, not quite in the same league! (at least 4 or 5 divisions lower!!).
I’ll let you know the outcome.
I think that you may have been subjected to a rogue support technician, and one too stupid to realise that he would be found out.
There have also been reports of very useful help from Samsung support too though.
Solved (hopefully).
re-install to day 1, and then reinstall the lot again (updates etc).
This time checked Safe mode, then made the backup.
So far, so good.
- You must be logged in to reply to this topic.