Win 1607 Login

Hello
I use to be able to apply a fix so I could bypass the splash screen and go right to login but I cannot.
Do you know how?
TY
Peter

 

There was a update for Windows 10 Version 1607 on Aug.2. Did you have trouble before or after the update?

 

After the update as I used to go right to login. The older fix does not apply.

 

If you're using W10 Pro, MS made changes and removed policies with AU (1607).

It looks like the below snip is relevant to your problem:

EDIT: there's a more recent post there that might help you revert to your old settings.

 

Thanks a lot; I have to look into this.

 

I don't know if you have multiple users on your computer. But, since I'm the only person that uses my computers, I automatically log in to my Desktops.

Open an elevated Command Prompt by right clicking the Start Button and selecting Command Prompt (Admin).

Type "control userpasswords2" (without the quotes) and hit Enter.

In the box that comes up, uncheck Users must enter a user name and password to use this computer and click Apply.

Enter your password twice and click OK. Click OK again and type exit in the Command Prompt window and hit enter.

From then on, you'll automatically log into your Desktop if it's what you wish.

 

If I get this correctly, I can then just avoid login. I would prefer to be able to go to login bypassing the splash screen and then login so my work is somewhat protected. This what I did before the update.
BTW, I am having an awful time with sluggishness since the update. Are you?
And thank you for the tip about directly accessing the pc.
Peter

 

you are the third person in less than 10 hours i have heard with similar complaints about sluggishness, please notify us if you begin having problems with courser glitching, freezes, blue screens, etc. it seems 1607 is really glitchy and it might be a good idea to roll back to the last update. heres a bit about what i mean.
http://forums.majorgeeks.com/index.php?threads/last-update-sluggish.308555/#post-1967862
and
http://forums.majorgeeks.com/index.php?threads/computer-is-freezing-up.308445/#post-1967819
both i believe are related to your problem also and it seems to revolve around 1607.

 

I may either image back to before the update or do a clean install.

 

i cant tell you what to do with all confidence until i hear from a few more experienced admins, but my recommendation (and not saying you should but if it was my personal comp i would cuz i brick machines for fun) would be to simply uninstall that particular update, or sys restore to just before it, and if that does not fix the issue, try a re-image. but yet again, im not the highest on the tech totem pole, im just a guy who has done alot in the last 20 years, and ive spent alot of time unbricking my own handywork. i dont want to be the one to lead you down a bad path, but for me it seems to be the logical solution.

 

Your suggestions seem solid.
I am currently imaging back to 7-22 as we speak.
I have to leave for a while but will report back.
I am concerned that the update will once again foil things up but cannot and really should not stop it. Lets hope it works.
Do you delete anything once the update is installed such as old files that could slow things down?

 

i am going to wait for a higher up to look before i go any further into the issue, i will say that there are ways to prevent windows 10 from auto updating (i gutted my os first day and still am running win10 beta from around february) but all in all, it would just be the 1607 update uninstall and then making sure that the previous version (i think its 1511 but i could be wrong) is functioning properly.

 

running CCleaner registry tool and cleaning tool should remove any unused registry keys left over from the update

 

http://www.howtogeek.com/223864/how-to-uninstall-and-block-updates-and-drivers-on-windows-10/
and here is how to prevent 1607 from coming back once it is gone

 

I'm back to 1511 and everything is running beautifully. I do not know if I should block the update - it may not be wise.

 

>>Could be dangerous. I ran the Windows cleaner but not the registry cleaner.

 

i run CCleaner reg tool almost daily and i do alot of uninstall and reinstalls, (mainy play testing games and programs) however i have used CCleaner to remove reg keys after uninstalling updates on win7 previously. as far as i know win10 is the same framework as 7 and i dont forsee any problems arising from it, just watch closely what it does before finalizing the deletion, and if it does really cause problems, i would say, you suggested a clean re-image before i did.
also hijackthis might be a better way to remove the reg keys if you are advanced enough to use it, because its super precise, however you have to tell it what to do step by step so it may be a lengthier more complex process. another alternative is after the uninstall using the fileshredder program from spybot 1.6.2 can be used to manually find the unused keys and delete them by hand. still recommend using ccleaner to find the exact filepaths though because it automates it.

and my first suggestion is simply system restoring to a point before the 1607 was installed.

 

im glad to know we have proof that 1607 is causing the problem. thank you for being the first to dive into rolling back, and confirming that 1511 is stable but 1607 is not.

 

you are right, doctor. it is for malware removal. but its file shred capability makes it useful and re-purposeable , either way i wont argue. probably not the best tool for the job.

 

I was just reading on my phone that the number of people complaining is massive.
Can I keep my image for awhile till this is sorted out - how do I keep the update from installing?

 

Assuming you're on W10 Pro, the following article should still be valid for 1511: http://www.computerworld.com/articl...r-upgrades-and-updates-in-windows-10-pro.html

 

I have not had problems with sluggishness though I have had slight "hangs" in Firefox but, that's all. Otherwise, Win 10 version 1607, build 14393.51 is operating normally.

I also run the Insider Preview which is now at build 14901.1000 (RedStone 2) and the Feedback hub asked how responsive this build is. I haven't worked with it enough yet to form an opinion.

 

Same here - three systems

 

"Works for me" = useless comment.

Windows has been such a personal system for so long, so many different settings and options, so many 3rd party software choices...

I've ditched 1511 three times on this rig, twice, 1511 and 1607, on my alt. rig. and once on my portable. Forced hardware driver updates causing issues, difficult to turn them off completely, even deferring updates/upgrades isn't easy or always successful. 1607 frozen for 5 days out of 10. BSODs after which no logged traces show are some of the lowlights.

Staying with W7 for the time being. I've missed only the ability to scroll any window, not just the active one, in the 3 days since I've been W10-free. I've (re)gained stability and time, I can now concentrate on the software I want to run, no more hours working through logs and searches trying to figure out workarounds, whilst waiting for the next lock screen that tries to force me to update.

W10 might be fine on single drive machines, new machines and for users who upgrade from a less than moderately tweaked W7/8.1, outside of that, the chances of it being a time wasting liability increases markedly.

 

Not entirely. For a balanced view it is necessary to make it clear that for many - the huge majority I suspect - it works without problems. Whether you personally like it or not IS useless, but as I see it it is a stable, feature rich OS that makes computing easy.

 

I'm not having any problems with Win 10 1607 (build 14393.51) on several systems.
I did have to re-run O&O ShutUp 10 again - as has been publicly advised - as this build does make changes that may not be wanted. It also reinstalls many Windows Apps that may have been removed/disabled in the earlier version. Reverting these changes, if wanted, is not difficult.
I have helped about 30 users to upgrade to Windows 10 and they generally let me know if they experience any problems. Apart from a few issues initially related to drivers, they are not coming back to me about any problems.
I am sure some people do have difficulties which may be related to their unique system, but even empirically I'm not seeing any such major issues with Win 10 suggested.

 

The OP's looking for a fix, not a balanced view.

 

The OP has received information about one possible fix (post #6) but I don't know what the 'splash screen' they refer to is. I log in by PIN and nothing has changed between 1511 and 1607 for me. A screenshot of the unwanted splash screen would have helped.

 

LOL, so post #4 was useless, eh?

 

I have no idea, which is why I can't comment. I can't see where the OP answered with their exact Win 10 version [edit: 'edition'].

 

The title suggests 1607, maybe you mean SKU?

 

Home or Pro or Ultimate or Enterprise. Post #4 specifies a 'Pro' edition.

 

I was addressing your opening comment in #25 which had nothing at all to do with a fix and was all about the problems you have had with Win 10

 

Max, they're SKUs, not versions.

If you delve a little deeper into #4 and the link provided, swap out the OP's word 'splash' for 'lock' and note his reply.

Earthling, my opening comment in #25 was ""Works for me" = useless comment."

The remainder was comparative, like it or lump it, it's more useful than a bald 'works for me' type statement.

 

Editions:
https://www.microsoft.com/en-us/windowsforbusiness/compare
http://wincom.blob.core.windows.net/documents/Win10CompareTable_FY17.pdf

And we still don't know the OP's edition.

 

Versions: https://msdn.microsoft.com/en-us/library/windows/desktop/ms724832(v=vs.85).aspx

SKUs: http://social.technet.microsoft.com...4.windows-8-1-editions-skus-and-features.aspx

 

Great second link thanks - it says 'Editions'

 

Look at the link above: social.technet.microsoftDOTcom/wiki/contents/articles/14374.windows-8-1-editions-skus-and-features.aspx

And the article title:

Windows 8.1 Editions (SKUs) and features

 

Yes that's great, thanks, I read it, both Microsoft and Technet refer to them as 'Editions'
From Microsoft:
'Compare Windows 10 Editions'
and
'Find out which Windows 10 edition is right for you.'
I appreciate you correcting my terrible mistake in post #31 (which I amended quickly) using the term 'version' instead of 'edition'.
Post #4 gives a fix for someone using the 'Pro edition'.
Let's hope the OP manages to solve the log in problem, whatever Win 10 'edition' they have.

 

Editions is the term MS use for consumers (advertising blurb), SKUs is the tern used internally, they're interchangeable but that doesn't mean that either, or both, terms mean 'version'.

Nice, something that most fora disapprove of but whatever floats your boat.

Read #4 and the linked article, it might help give you an alternative comprehension of #1, 3 and 7.

 

I think everyone here is a consumer.

 

So are MS. So what?

 

Well you mentioned it, so no idea lol

 

Very droll, now go study the other suggestions I made, eh?

 

Thanks. I've read them in detail and bookmarked the links in case anyone whose systems I help with have such a problem. Luckily, I don't have the issue and I'm not the OP. Have a great day!

 

After having the anniversary installed it was fine. Over time issues of sluggishness arose. It is quite obvious when you check www that many are having issues. Those who did not, I am glad for you.
I reimaged to build 1507 and have deferred updates for a while.
Both machines experienced the same slowness and trouble with the mouse.
I hope something is done so I can remove defer.

 

That is version 1607 (build: 10.0.14393) If you say it was all fine, then not sure which version and build you had those problems on.

You can see all the versions, and builds, here:
https://en.wikipedia.org/wiki/Windows_10_version_history

 

1511, sorry for the error