Windows 10: login "welcome" stays longer than usual on ssd after sept update

hey guys...

i dont know if its the september update but i have a ssd and login used to be a flash like 2 secs..welcome wouldnt stay more than a second...

now when i log in welcome is their for 3-4 seconds before the desktop loads....this never happened before...

any ideas on how to get it back the way it was?

my ssd has alot of space on it....i ran dism restore....i made sure the startup settings were the same...no additional programs loading in the back...

thanks again...

:)

 

Wifi Disconnecting after Sept, 2016 windows update

After the Sept, 23 2016 automatic windows update, the wifi was no longer stable and disconnects several times during the day.

The wifi adapter shows an update occurred during the Sept 23 update.

I have an ASUS computer that using a Realteck 8821 Wireless LAN 802.11 ac PCI-E NIC.

I have turn off wifi sense, turned off option to power save, disabled and enable it. Windows claims the driver is updated.

Any other suggestions?

 

Can't login to new computer w/Windows 10

Hi,

Thank you for your reply.

• 
  Are you able to login to Microsoft Account on Web?
  
• 
  Have you installed any language pack?
  

I suggest you to follow the steps below and check if it helps.

Step 1: I suggest you to select the appropriate language in login screen at the bottom right corner and check if it helps.

Steps 2: Use On-screen keyboard in the login screen to login and check if it helps.

Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help.

 

Win 10 Sept 2016 Update

1. Recap: You replaced the SSD and did a clean install of Win7 Professional edition & installed Norton 360 on 30 July 2015, the upgrade to Win10 was offered on or about 06 Aug-15, after some set backs & errors, Win10 finally installed via Windows
Update [?] using "Express Settings" on 10 Aug-15. You then upgraded to Win101511
Home edition on 27 November 2015, after which you encountered many problems, usually after installing a cumulative update for Win10 1511. Assuming that's correct (so far):

2. Did you back up any personal data prior to replacing the SSD and then restore it to the new SSD after you did the clean install of Win7?

3a. Did you upgrade from Win7 Professional to Win10 Home last August and if not, how did you end up upgrading from Win10 Professional to Win10 1511 Home in late November?

<EDIT>

3b. Did you run the Win10 Upgrade Assistant before you upgraded to Win10 using "Express Settings" on 10 Aug-15?

</EDIT>

4. Was Win10 1511 offered & installed via Windows Update in late Nov-15 or did you install it manually?

5. Did you have to install any updates for Win10 1511 manually (vs. via Windows Update)?

6. Can you tell me when (approx. date) Win10 1607 was installed? [Tip: Chances are it was
after KB3176937 was installed.]

7. Was Win10 1607 offered & installed via Windows Update or did you install it manually?

8. KB3189866 (released 13 Sept-16) was never offered via Windows Update and you had some Norton 360 issues on or about 26/27 September 2016 - during which time (or possibly a day before) KB3176936, KB317937, &
KB3193494 [I assume] may have been installed, correct?

9. Are Compatibility update for upgrading to Windows 10 Version 1607: August 23, 2016 (KB3176937) &Cumulative update for Windows 10 Version 1607: September 20, 2016 (KB3193494) still listed as being installed on 25, 26 or
27 [<=PICK ONE] Sept-16 in Installed Updates (not Update History)?

10. Were you prompted to install a program update (upgrade) for Norton 360 on 26 Sept-16?

11. Tell me about the "Norton Autofix Notification" you encountered on 27 Sept-16?

COMMENTS:

• The freezing may be Norton-related.
• Many of the installation dates in your penultimate reply disagree with each other, hence the iffy-sounding questions above.
• Careful with KB numbers & typos - it's usually better to copy/paste them then type them. The longer you look at 'em, the blurrier they get! If you make a typo (e.g., KB317937 vs. KB3176937; KB317934 vs. KB3193494),
  there's a good chance I'll copy/paste it without noticing it was a typo - especially at 2:35 am!