Subject: Mobile | July 19, 2015 - 10:43 PM | Scott Michaud
Tagged: Android, microsoft, windows, windows 10, cortana
When it graduated from high school, Microsoft was voted “least likely to have an open relationship with itself”. Well who's laughing now, member of the Yearbook Committee? You thought you were so clever, sitting in the back of the late bus for students in extra-curricular activities, giggling as you doodled in your Five Star binder. Even though they always hogged the Windows seat, maybe they would have opened it up for a little fresh air in the Summer time had you taken the time to ask.
Image Credit: Ars Technica
While Cortana is first and foremost a Windows 10 feature, it will appear on iOS and Android as well. Peter Bright of Ars Technica got in on the pre-release, invite-only beta and walked through the features. He notes that, while many have complained about crashes, his experienced wasn't marred with stability issues. On the other hand, because Cortana is not as deeply integrated into the operating system, despite the laundry list of permissions it requests, he expects that most users looking for a digital assistant will look to Google Now on their Android devices, even if they use Cortana on Windows 10.
Image Credit: Ars Technica
There really wasn't a whole lot of note in the article though, at least in my opinion. There are a few interesting screenshots, but it basically looks like someone grafted the Cortana fly-out menu from Windows 10 onto a fullscreen mobile device. Even though I already saw the similarities in the Windows 10 Technical Previews, it is funny to see it so explicit.
No release date has been set for Cortana on Android or iOS.
Subject: General Tech | July 14, 2015 - 12:43 AM | Scott Michaud
Tagged: windows 10, windows, microsoft
UPDATE (July 14th, 6:15pm ET): The change is now in effect. Going to the Insiders page at insider.windows.com has the PC link disabled and a message explaining that you're too late.
See you at RTM!
Windows 10 is launching two weeks from Wednesday. Microsoft has set up a reservation system for Windows 7 and 8.x, apparently to create a queue for early adopters in before their “could care less” demographic. This was not available on Windows 10 Insider Preview, which we later found out is because Insiders are already at the front of the line. This is important, given today's announcement.
July 13th, which is thankfully not a Friday, will be the last full day to receive ISOs or new builds over Windows Update. By some point tomorrow, these will be taken offline. We will be transitioned over to “production channels” for our next build and ISOs will not be provided. Also, pre-release keys will no longer activate. ISOs will return at some point, but they want to get everyone using their updating platform to make sure they work.
They also say that we will receive at least one new build before release.
Obviously, we are getting close so things are going to start changing. I wonder how long we will stay on RTM branch before Microsoft pushes Insiders forward. We know that Microsoft has already forked development into a 105xx line of build numbers, which is very likely to be post-launch updates. I am not sure that they would push those out over production though, so you would think that Insiders will be on RTM-based builds for at least a little bit.
Today might be your last chance to get in on Windows Insider for a bit, though.
Subject: General Tech | June 8, 2015 - 12:35 AM | Tim Verry
Tagged: windows, remote management, powershell, openssh, mac os x, linux
Citing both leadership and corporate cultural changes within Microsoft, the PowerShell team – led by Team Group Software Engineering Manager Angel Calvo – excitedly announced support for OpenSSH earlier this week. Specifically, the team (finally, after the third such attempt) got the go-ahead from Microsoft's leadership and plans are underway to natively support OpenSSH in PowerShell as well as to contribute to the OpenBSD project on behalf of Microsoft.
Details are scarce, but this is great news for system administrators and a nice extra feature for enthusiasts that like to dabble in those "other" operating systems (which is to say, pretty much every OS except Windows) and remotely access them over a secure SSH connection to perform maintenance or transfer files.
Currently, Windows users need to use third party tools to support SSH clients and servers such as PuTTY (and PSCP) and Cygwin (not pictured).
Until now, users have had to rely on third party tools such as PuTTY, Filezilla, and Cygwin among others for their SSH, SCP, and SFTP needs. Accessing Linux machines using PuTTY is fairly straightforward, but going the other direction and trying to set it up so that you can access a Windows machine from a Linux machine over SSH could certainly be made easier and more stable. Native support for OpenSSH would mean both client and server support built into Windows and support for SSH, SFTP, and SCP protocols.
From the MSDN blog and this twitter exchange, OpenSSH in Windows PowerShell is still in its infancy. It will not be launching with the rest of Windows 10 on July 29th, but with the level of customer interest hopefully pushing the refreshed Microsoft to make this a priority we may see it within the next year or two, and certainly before Windows 11!
Are you ready to get your native SSH on using PowerShell, or will you be sticking with your current third party implementations?
Subject: General Tech | June 4, 2015 - 11:40 PM | Scott Michaud
Tagged: microsoft, windows, windows 10
Gabe Aul said on Twitter that Microsoft will release Windows 10 Build 10130 to members of the Insider Preview Slow Ring. He did not give a date, but noted that just one blocking fix is preventing the release. This build was released to Fast Ring users last week and had three known issues. Since then, two were patched via Windows Update, leaving just “Flyouts from Taskbar fail to fly out.” Presumably, this is the issue that they are hoping to fix before pushing the build to Slow.
When the update is released to Slow Ring, it is accompanied by ISOs that can be used to clean-install a PC up to that point. While this delay is to force a segment of users to test the in-place upgrade functionality, I expect this also keeps enterprise evaluators on builds that are more polished. Installing Windows from an ISO might not convey the quality-difference of any two neighboring builds like selecting branches in Windows Update would subconsciously portray.
Microsoft seems to be at the merge and polish stage of Windows 10 development. Builds should start feeling more clean than new as the days roll forward toward July 29th. Major new features are probably going to be done in branches for later releases, similar to what we would consider “service packs”. That's just my assumptions, though.
No Longer the Media Center of Attention
Gabe Aul, of Microsoft's Windows Insiders program, has confirmed on Twitter that Windows 10 will drop support for Windows Media Center due to a decline in usage. This is not surprising news as Microsoft has been deprecating the Media Center application for a while now. In Windows 8.x, the application required both the “Pro” SKU of the operating system, and then users needed to install an optional add-on above and beyond that. The Media Center Pack cost $10 over the price of Windows 8.x Pro unless you claimed a free license in the promotional period surrounding Windows 8's launch.
While Media Center has been officially abandoned, its influence on the industry (and vice versa) is an interesting story. For a time, it looked like Microsoft had bigger plans that were killed by outside factors and other companies seem to be eying the money that Microsoft left on the table.
There will be some speculation here.
We could go back to the days of WebTV, but we won't. All you need to know is that Microsoft lusted over the living room for years. Windows owned the office and PC gaming was taking off with strong titles (and technologies) from Blizzard, Epic, iD, Valve, and others. DirectX was beloved by developers, which led to the original Xbox. Their console did not get a lot of traction, but they respected it as a first-generation product that was trying to acquire a foothold late in a console generation. Financially, the first Xbox would cost Microsoft almost four billion dollars more than it made.
At the same time, Microsoft was preparing Windows to enter the living room. This was the company's power house and it acquired significant marketshare wherever it went, due to its ease of development and its never-ending supply of OEMs, even if the interface itself was subpar. Their first attempt at bringing Windows to the living room was Windows XP Media Center Edition. This spin-off of Windows XP could only be acquired by OEMs to integrate into home theater PCs (HTPCs). The vision was interesting, using OEM competition to rapidly prototype what users actually want in a PC attached to a TV.
This leads us to Windows Vista, which is where Media Center came together while the OS fell apart.
Subject: General Tech | April 26, 2015 - 11:31 AM | Scott Michaud
Tagged: windows 10, windows, microsoft
There are still a few users on old Windows 10 Technical Preview builds from 2014. In a few days, there won't be: their computers will refuse to boot. The affected builds that will completely brick themselves on April 30th are 9841, 9860, and 9879. You cannot accuse Microsoft of surprising users though, because Windows has been notifying them since April 2nd and force-rebooting every three hours since April 15th if they didn't take the warnings seriously. The current batch of builds are valid until October.
WinBeta has linked this policy to Microsoft's rumored piracy policy. My thoughts? No.
This is actually typical of Microsoft when it comes to pre-release operating systems. In fact, the only difference between this and Vista's pre-release (ex: “Beta 2”) expiration is that Microsoft relaxed the reboot time to three hours. It was two hours back in the Vista era but otherwise identical. That policy only applied to the previews then, and I see no reason to believe that it will be extended to released operating systems now.
Granted, with the Windows 10 continuous update structure, it does raise concern about what will happen if/when Microsoft releases a build that users don't want. For instance, imagine Microsoft decides to cut off legacy support for Win32 -- will customers have the ability to opt-out of the upgrade treadmill and continue to use applications that are then unsupported, like practically every Steam game they own?
But I see no reason to think that this policy has anything to do with that.
Subject: General Tech | April 21, 2015 - 11:00 AM | Scott Michaud
Tagged: windows 10, windows, microsoft, amd
The CEO of AMD is an unexpected, but probably very accurate, source when it comes to knowing the Windows 10 release date. First off, the news broke on a quarterly earnings call. When you make a statement on those, you have a strong legal obligation to be telling the truth according to the knowledge that you have at the time. Also, as a major hardware vendor of CPUs and GPUs, her company would have been notified by Microsoft so that they could plan development of graphics drivers and so forth. It also aligns with the “Summer” announcement made last month by Microsoft.
Of course, this led to a flurry of comments that claim three months will not be enough time to bake a successful product. Others, naturally, claim that Microsoft has been developing software for long enough to know that they can finish their product in three months. Still others shrug and say, “Yeah, you both make sense. I'm going to go play some Grand Theft Auto.”
One aspect that I don't see mentioned enough is that Microsoft has multiple projects and teams on the go, and we only see a fraction of what is being done in our Insider branch. Despite the narrative that Microsoft wishes to avoid another Windows 8 fiasco and they want their users to guide development, they have alluded that a major reason for the Insider program is to test their build delivery system. While I am having a bit of a hard time finding the supporting quote, I did find one reference to it being the reason for ISOs being delayed.
And finally – we heard from you loud and clear you want ISO images of the new builds we release. We felt it was important to listen to that and give you what you want – but there’s a catch. Getting the update & install data from our Preview Builds mechanism is super important for us. It helps us ensure smooth ESD distribution, download, and upgrade success for this program going forward, and also will help us ensure great upgrades for people once we release Windows 10. So we’re going to release the ISOs at the same time as we publish to the Slow ring. That means if you want to be FIRST and FASTEST to get the build, you’ll need to use our Preview Builds mechanisms (either automatic or Check Now in PC Settings to download.) If you must have an ISO you’ll have to be a bit more patient. I hope that you’ll consider that a fair tradeoff.
So what is my point? Basically, it is difficult for us to make assumptions about how baked Windows 10 is from our standpoint. They are being more open with us than ever about their development methods, but we don't know certain key things. We don't know what final feature set they plan. We don't know how much work has been done on any individual feature since it was merged into a build that we saw. We also don't know how much has been done by third parties. In some cases, a release in three months could equate to like, six months of work for a specific team since their last contribution was merged. I do think that any major feature we see at BUILD will pretty much be the last additions to the OS before it launches though, unless they have a surprise that will surface at E3 or something.
Also, remember that the things they show us are slanted to what they want feedback about.
Subject: Systems | April 20, 2015 - 10:00 PM | Jeremy Hellstrom
Tagged: windows, SoC, mini-pc, Intel, ECS, Bay Trail-M
When Sebastian reviewed the LIVA X he focused on the performance of the device as an HTPC running Ubuntu ... before attempting to determine its effectiveness in creating a peanut butter and banana omelette, but that is a different story.
Overclocker's Club took a different tack, examining how it would perform for light gaming duties. On default settings the LIVA X managed 517 in Sky Diver, 1198 in Cloud Gate, 14200 in Ice Storm, and 9598 in Ice Storm Extreme. This would make it effective at playing mobile games or even playing through legacy games available through GoG or the Internet Archive; they tested CivV as a more modern title and while playable it wasn't great. Check out the full review for the other benchmark results.
"The ECS LIVA X surprised me with its small size and completely silent operation. I was able to surf the internet and do work on it very quickly. I enjoyed using it and experienced no problems with browsing the internet, using Office applications, or watching streaming videos on Netflix. Amazon Prime would occasionally lag a little – usually when the HUD would pop up."
Here are some more Systems articles from around the web:
- Get Your Old Rig Gaming Ready on a Tight Budget @ eTeknix
- Intel NUC 5I3RYH (DinoPC) @ Kitguru
- OcUK Ultima Finesse Blackhole Gaming PC @ Kitguru
Subject: General Tech | April 17, 2015 - 11:00 AM | Scott Michaud
Tagged: windows xp, windows, microsoft, google, EoL, chrome
It has been a year since Microsoft cut off extended support for Windows XP including Internet Explorer security updates for the platform. Yeah, I know, it doesn't feel like it. Other browser vendors announced that they would continue to target the retired OS after Microsoft washed their hands of it. At the time, Google said they would give at least 12 months support, which brings us to yesterday.
Now Google is extending their commitment to the end of the year. They did not say that it was a hard deadline for their customers, but they also did not add an “at least” qualifier this time. The browser vendor wants people to upgrade and admits that they cannot genuinely provide a secure experience if a known issue bites everyone at the OS level. You can keep training the guard at the door, but if your window falls out, mind the pun, then it is still dangerous to be inside.
Granted, we have not seen a major attack on XP over the last year. You would have to think that, even if the attacks are sophisticated, some of the victims would have noticed and reported it to someone. Still, I wonder how it keeps surviving, especially since I would have thought that at least one vulnerability in the last twelve Patch Tuesdays could be ported back to it.
Maybe it is too small of a target?
Subject: General Tech | April 10, 2015 - 11:30 AM | Scott Michaud
Tagged: windows 10, windows, microsoft, build 10056
Moving up five steps from the 10051 leak that was published just a few days ago, another build was leaked: 10056. The first thing Neowin, who reported on the WZor leak, noticed is the new Recycling Bin icon. People were not a fan of the change that occurred with 10041, which honestly looked like it was out of a Mike Judge cartoon. It is now a semi-transparent, almost prism-shaped bin from a dimetric viewpoint. That should make some people happy.
Also visible is a new “Virtual Desktop” icon and a relocation of the power menu button from the top right to the bottom left. This shift puts it alongside every other control except the Start menu's fullscreen button, which remains in the corner. To me, this looks a lot more organized.
On the topic of future builds, Gabe Aul seems to be implying that Slow Ring users would not get 10049. This likely means that Fast will get another build soon, which we would expect to trickle down to the “Slow” users on 10041. The proximity to Build confuses that slightly though. It is possible that Microsoft will do what they did with 9926 and delay Fast builds so they can have a highly-tested preview build (“Technical Preview 3” or something) pushed to both Fast and Slow rings to surprise attendees of the conference. Well, as much as they can hide stuff given that every few builds are being dissected online. I'm sure they have a lot of work being done in external branches though.
Either way, we'll find out soon... even if that's by not finding out soon.