|
Sign-in with your Microsoft account.
|
|
|
|
|
Why?
And if I have none?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
That was just a solution to the problem you were facing. Not sure, I have an answer for Why?
|
|
|
|
|
Its not a new requirement to have a Microsoft account, I know VS2015 had the same requirement if you wanted to use it beyond 30 days too.
|
|
|
|
|
Not community edition - I have it without far beyond 30 days...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
That's strange, 2015 certainly stopped working for us after 30 days without a Microsoft account.
|
|
|
|
|
com-13 had the same.
I set up a bogus ms account and used that (need to go to About - Update License or similar)
After the licence was updated I added a firewall rule to block it's outbound connections.
Working fine like that, no nags, no ms spam.
Sin tack
the any key okay
|
|
|
|
|
Lopatir wrote: After the licence was updated I added a firewall rule to block it's outbound connections.
Working fine like that, no nags, no ms spam.
Can we make the same with the Windows Updates? 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Why?
Because you want it for free.
Kornfeld Eliyahu Peter wrote: And if I have none?
Then you can't have it.
|
|
|
|
|
2015 isn't that picky...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
It is, at least later updates (I'm not sure about initial release).
|
|
|
|
|
Same experience here. After 30 Days I needed to Login with an MS account.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
The interesting thing is that after installation it displayed a valid community license.
Now I logged in and run 'Check for an updated license'. Now 2017 displays a valid community license again... I signed out (and removed associated account, just like in 2015) to see if it will fail back to trial in next month...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Windows 7 was not that picky either
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: 2015 isn't that picky...
My 2015 Community Edition was. Stopped working without a sign on. You sure you didn't install the Pro version of 2015 (which won't complain about not being signed in)? Perhaps from an MSDN ISO?
|
|
|
|
|
See it for yourself... vs2015.png (53.4 KB)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: And if I have none?
Then get one.
You can never have too many junk e-mail accounts.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Microsoft pushing us along to newer and better. I work in the embedded world with their products. The problem? Microsoft really isn't into understanding embedded (one project I support has units in the field since 2005), they are much more into "oooo shiny, look what's new, oh, my new OS doesn't support that tool any longer, sorry."
I'm in the process of having to support my development environment on a Windows 7 VM. Up early this morning - my Windows 7 VM needed to apply updates. Stuck at "Installing update 2 of 5" for 30 minutes now.
Recommendation: if you have a beloved Windows 7 machine that you use to get your work done, prepare stay on Windows 7. If you are being forced to go to Windows 10 (I know this is about to happen to employee co-workers), get your environment into a VM before you toss your old machine, or IT takes your machine. I know VMware allegedly can do this, and I just saw an article about hyperV supporting something like this as well (if anyone has actually done this, please comment).
If, of course, all you do is Visual Studio <the latest="">, C#, Office, etc, you should be fine.
Damn, caffeine has kicked in and I'm still at "2 of 5".
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Ahem. Solution to stuck at 2 of 5? power cycle. actually recommended by MS. 
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I'm in the process of taking the opposite approach, installing 10 into a vm (virtualbox) on my win 7 host.
Benefits as I see them:
1. a machine that will start up faithfully every day (so I can get into cp)
2. The VM provides a very standard machine - no funky driver worries
3. can take a snapshot before and after major updates/installs - so if when the SHTF fast recovery
4. [Not that I have anyone telling me I must go 10] run full screen, looks just like a real fulltime 10 machine if your boss comes around.
Much more sane option, and can get it going much faster,
and don't have to worry that I might break my 7 trying to squeeze it into a box.
Sin tack
the any key okay
|
|
|
|
|
Hindsight.... is bliss, I think I'm mixing metaphors 
I actually have a Windows 10 VM that was installed on my Windows 7 laptop, so I could play with the OS. I went Windows 10 mainly because I had too - vendor only sold the laptop with Windows 10. I actually have Windows 7 running on 10, but it's still a touch clunky.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I lay this at the feet of the horribly incompetent embedded leadership; the ones who had a lock on the embedded space in 2006 and then stopped work for five years. We're now going on four years with Embedded Compact 2013.
(Of all the departments I've dealt with at Microsoft, the embedded ones were the worse. Once reported a problem and they lost their sh*t. For a moment, I thought I was dealing with the idiots at Wind River.)
|
|
|
|
|
I've updated to the Windows 10 Creators Update. I received this error for every file unzipped while unzipping a fairly large code archive. It's solution? To reset the defaults away from Chrome and "safely" back to Edge. Result? The unzip took 10 times longer than it should have and Explorer constantly restarted.
Seriously Microsoft: you've dipped down to seriously desperate measures to get people to switch to Edge.
cheers
Chris Maunder
|
|
|
|
|
And why? What's the BFD if we use this browser or that to access this and that? I don't get it. Can't be just bragging rights.
|
|
|
|
|
Chris,
Chris Maunder wrote: Seriously Microsoft: you've dipped down to seriously desperate measures to get people to switch to Edge.
That's a terrible accusation. Just want to point out that this is caused by old third-party software such as Winzip that attempt to directly modify registry keys for file association and other user preferences.
The Windows 10 operating system now maintains a checksum/hash of the 'Default App' user preference registry key values. When a direct registry change is detected we validate the checksum. If the checksum fails then the user defaults are restored. If the third-party application repeats the registry change... you may get into an infinite loop of user preference restoration.
Pass the word around... software developers should no longer directly modify these registry keys. Users may use the 'Set Program Access and Computer Defaults' to modify file types and associations.
Best Wishes,
-David Delaune
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
