thewayne: (Default)
Apparently testing was pretty good and MS has decided to launch Recall for Windows 11. They have made it opt-in, thus you must specifically enable it before it starts snapshotting your system. This is good.

But there's something better: it doesn't run on most machines out there!

Recall requires a system with an NPU, a Neural Processing Unit. These are additional chips installed on the motherboard that have only been in the sales channel for about a year. I'm also pretty sure that these computers came with a keyboard that had a Copilot key on the bottom row to the right of the space bar, though there may be keyboards with that key sold with computers without the NPU. So if your PC is from 2023 or older, it doesn't have an NPU and won't run Recall.

And yes, there are laptops with NPUs.

Recall is part of a feature package called CoPilot+. From the article: "The only consumer processors that currently support Copilot+ are Qualcomm's Snapdragon X Elite and Plus chips, Intel's Core Ultra 200V-series laptop chips (codenamed Lunar Lake), and AMD's Ryzen AI 300 series. Copilot+ features have generally been coming to the Arm-based Qualcomm PCs first and to x86-based Intel and AMD PCs later; Recall and the improved Search are available for both Arm and x86 PCs, while some Click to Do features are currently only available for Arm systems."

Of course there is the problem that when you go to replace your current system in a few years, it's likely that your new box will contain an NPU and you'll get nagged to activate Recall.

https://arstechnica.com/gadgets/2025/04/microsoft-rolls-windows-recall-out-to-the-public-nearly-a-year-after-announcing-it/


In an interesting sidenote, Intel's AI chipsets are not selling well, people are really wanting the previous generation known as Raptor Lake. The AI chips are known as Lunar Lake and Meteor Lake, I think one name designates laptop chips.

Intel is having all sorts of corporate problems and it's being felt up and down the product line. They're looking at selling off divisions to hunker down and get their act together.

https://www.tomshardware.com/pc-components/cpus/intels-ai-pc-chips-arent-selling-instead-last-gen-raptor-lake-booms-and-creates-a-shortage
thewayne: (Default)
It's moving back into the beta preview builds, which means they're hoping for a public release in coming months.

As if we need a reminder, here's some reasons as to why it's bad.

1. It will eat approximately 15% of your TOTAL disk space.
2. If you're running a solid-state disk, it will increase your disk wear. This means your disk will fail sooner than it should. This is not as problematic as your traditional spinning rust hard drive.
3. Increased CPU use, possibly laggier system. We don't know how much CPU resource it will use IRL.
4. While it is theoretically secured behind your login, we don't know how secure it is. The last time around for it, it was capturing banking information, medical info, SSNs, etc.
5. We don't know if it might be reporting things upstream to someone. Guaranteed that once it gets into the beta program, much less general release, there will be privacy and security boffins who will be watching their firewall logs for what activity it is generating.

I expect we can anticipate further privacy issues with this thing on-going. And if you're not running it, and you send sensitive or confidential information to someone who is running it, well, your information will be hoovered up by their system.

Broadly speaking, it's probably not a good idea for a lot of people. I certainly do not recommend it. The article has recommendations on how to disable it, I don't think we have solid information on how to uninstall it at this time since it is not an actual released feature yet.

https://gizmodo.com/windows-controversial-recall-is-back-heres-how-to-control-it-2000589002
thewayne: (Default)
Recall, if you recall, is their replay "assistant" that no one seems to particularly be asking for. It takes screen shots of your computer and stores them so that you can look back if you lose information. During the first tests of it we learned that the storage of said snapshots were not secure, so someone who'd infiltrated your computer could conceivably see banking credentials, medical records, etc.

From the article: "Originally planned for October, Recall will now be available for preview with Windows Insiders on Copilot Plus PCs by December."

and

"Earlier this week, Microsoft again clarified that Recall will not be mandatory on Copilot Plus PCs, and will be an opt-in experience that can be fully removed."

It'll be interesting to see the blowback when this thing finally deploys, especially if it isn't fully opt-in.

https://www.theverge.com/2024/10/31/24284572/microsoft-recall-delay-december-windows-insider-testing
thewayne: (Default)
It was announced a while back that the new standard PC keyboard would now have a Microsoft Copilot key on it that would launch Microsoft's AI/LLM assistant. A new developer build has been released that allows that key to be remapped for other functionality than to launch Copilot, presumably one such option is to make it a dead key entirely in the event of accidental strikes.

If your keyboard does not have this key, running this remap doesn't do anything.

I've seen the Copilot key in the wild, but a lot of the third-party keyboards still don't have it. Knowing that I can turn it off is a nice thing for me. I have used Copilot before, it's mildly useful and nice that you don't have to sign in to it like ChatGPT. But I find the image generator to be useless for creating comics.

https://www.neowin.net/news/windows-11-dev-build-261201930-is-out-with-copilot-key-remapping-windows-sandbox-and-more/
thewayne: (Default)
Of course it is!

In a recent developers build, Recall was shown as something that could be removed in Windows Features. This is apparently a bug and will be removed from the Features applet in a future update. The Verge reached out to Microsoft to try and find out if Recall will be removable but did not receive a direct answer.

In the EU, Microsoft was required to make their browser removable, presumably the same thing will be required for Recall. So hopefully some clever boffins over there will find the registry switches to let us do it over here.

https://www.theverge.com/2024/9/2/24233992/microsoft-recall-windows-11-uninstall-feature-bug

https://it.slashdot.org/story/24/09/02/2241242/microsoft-says-its-recall-uninstall-option-in-windows-11-is-just-a-bug
thewayne: (Default)
They're still going to migrate some of the functionality into the Settings app on an unclear timeframe. Whether or not this is clearing up fuzzy wording or actually changing their mind after blowback from users is unknown.

https://arstechnica.com/gadgets/2024/08/microsoft-formally-deprecates-the-39-year-old-windows-control-panel/
thewayne: (Default)
This was kind of inevitable, so many things are moving there and sometimes it's hard to what obscure thing you're looking for is where. In the end it will probably be a good thing, but it'll take a decade before it's stable. ;-)

https://support.microsoft.com/en-us/windows/system-configuration-tools-in-windows-f8a49657-b038-43b8-82d3-28bea0c5666b

https://it.slashdot.org/story/24/08/23/031251/microsoft-says-its-getting-rid-of-control-panel-in-windows


In other Windows news, Microsoft announces the return of Recall. That's the system where your operating system watches everything you do, OCRs it and stores it in a local database to help you remember what you were doing in the past for your convenience. This was announced back in June, and it was discovered in beta deployments that there was absolutely no security being deployed in the database in terms of encryption or permissions, so if someone gained access to your PC - which never happens - then they could see your bank credentials, credit card numbers, health insurance info, you know - trivial things.

Details have not yet been released as to what security protections have been put in place. A non-existent Microsoft PR flack was quoted as saying "Trust us!"

The revised feature will go to Insider Program testers in October. Microsoft says more details will be disclosed at that time.

https://arstechnica.com/gadgets/2024/08/microsoft-will-try-the-data-scraping-windows-recall-feature-again-in-october/

https://tech.slashdot.org/story/24/08/22/1648253/microsoft-will-try-the-data-scraping-windows-recall-feature-again-in-october
thewayne: (Default)
A forthcoming version of Windows 11 known as 24H2 will enable Bitlocker device encryption (FDE) by default. This can be turned off if you want to get into Control Panel and deactivate it. The article notes that Tom's Hardware found that FDE can slow down disc access by 45% on solid-state drives. Additionally, Microsoft requires that the encryption key is uploaded to your Microsoft cloud account, meaning they have the means for decrypting your drive.

MS holding the key to your drive is a theoretical vulnerability. I have not read of them cooperating with authorities in the decryption of drives, much like Apple has not, though in Apple's case, they don't hold keys and cannot.

Personally, I don't think disk encryption is a good idea for the average home user. You should maintain good backups and keep them disconnected from your PC, preferably in a fire-proof lockbox or off-site. Have two sets (or more) and rotate between them so you have fall-back points if one of the backup sets fail.

We have a concept in IT that backups don't exist until you test them or need them, until that time they just exist in a void. When you pull them out and try to restore from them, that's when you find out whether or not they're any good. Backup disks and tapes fail, which is why if you value your data you want multiple copies to reduce the chance of one copy failing.

https://www.theverge.com/2024/8/14/24220138/microsoft-bitlocker-device-encryption-windows-11-default

https://tech.slashdot.org/story/24/08/14/1559240/microsoft-is-enabling-bitlocker-device-encryption-by-default-on-windows-11
thewayne: (Default)
Most of the systems affected are back working, but the remainder still accounts for a rather staggering 250,000 PCs and servers. My guess is these are the hardest hit and are either physically difficult to access or encrypted and might need to have the drive replaced and rebuilt from scratch.

Oh, the Uber Eats gift card debacle has been resolved. It's still a debacle, but apparently the cards that were sent out are now actually redeemable.

So why is the European Commission to blame? Let's get technical.

The core of an operating system is its kernel. This is the set of programs that provide its basic operations and core security. Obviously this is the most important part of the OS, and the part that you want to protect the most. Preferably, as the maker of the operating system, you don't want anyone to have direct access to the kernel.

Linux and Apple Mac do not allow access to the kernel, not even for anti-virus and anti-malware applications. They have a framework that allows those sorts of programs to run and defend the kernel, but not actually link into it. Thus, they were completely unaffected by the ClownStrike event.

But because of Microsoft's overwhelming market domination and ubiquity, the EC didn't like that everyone was banned from kernel access for their third-party software for things like malware and virus protection and required that Microsoft literally and actually break their security model to allow such kernel access. The alternative was that they couldn't sell Windows user or server software in Europe, and there was no way that was going to happen. So Microsoft broke the security protections that Windows had, and ClownStrike broke Windows.

Now the big question is what happens in the future to prevent a similar event? Microsoft says they are evaluating newer frameworks, more along the lines of what Linux and Mac are currently doing, to remove ClownStrike and similar software from the kernel to keep a repeat event from happening again. I would suspect that the EC regulators will take a look at what this cost the world-wide economy - estimated at over $5 billion dollars - and see that Apple and Linux allow third-party products to work well with their operating systems and give MS permission to lock down their kernel in a more secure fashion.

Which will make things better, but will also take some time to roll out.

https://arstechnica.com/information-technology/2024/07/97-of-crowdstrike-systems-are-back-online-microsoft-suggests-windows-changes/
thewayne: (Default)
I've been using Paint a lot recently, doing screen captures and snips for some documentation writing. One thing that's infuriating about it is that by default, it wants to save docs as PNGs, and you can't default it over to Jpeg!

But there's a trick....

Click on File, Save As, then you'll see a list of formats it can save in. Right-click on Jpeg and there's an option to creating a shortcut on the toolbar. Of course, you have to make the toolbar visible.

I prefer keyboard shortcuts, but I'll take this as a bit of a labor saver.
thewayne: (Default)
After suffering TONS of blowback in the press and industry, Microsoft is pulling the playback feature that took snapshots of what you were doing on your computer and saved them. The issue being that the save was unencrypted and readily accessible to anyone who could sign on to the PC: such as spouse abusers, hackers, etc. Why it was not encrypted from the get go, I don't understand.

Privacy? Who needs privacy! It's nifty! Nifty > privacy!

There were ways to deactivate the Recall feature, how easily it could be turned off is a matter of some debate. Microsoft and other vendors are also infamous for silently turning on things with updates that users had previously turned off.

CoPilot+ goes live June 18. *sigh*

https://www.windowscentral.com/software-apps/windows-11/microsoft-postpones-windows-recall-after-major-backlash-will-launch-copilot-pcs-without-headlining-ai-feature

https://it.slashdot.org/story/24/06/14/0318213/microsoft-postpones-windows-recall-after-major-backlash
thewayne: (Default)
FINALLY!

While integrating 7Zip file compression into Explorer was no big deal, it'll be nice to have it there from the beginning. The Tar support will also be useful. But the version control, that's going to be very useful for casual developers who don't want to mess with installing Git or similar repo controls.

https://www.theverge.com/2024/5/21/24161785/microsoft-windows-file-explorer-version-control-7z-tar

https://tech.slashdot.org/story/24/05/21/2238246/microsoft-is-making-file-explorer-more-powerful-with-version-control-and-7z-compression

The /. discussion has a lot of talk about Total Commander, Double Commander, and Directory Opus.
thewayne: (Default)
Meanwhile Windows 11 adoption rate DECLINES to below the 26% mark after hitting a high of just over 28%.

I'm running 11 Pro on my desktop at home. But given the choice, I prefer 10. I can't go back to it, don't have the media. And it's about to go to paid-for support, which I don't want to mess with. I have not yet found any feature in 11 that benefits me, in fact I had to find a workaround to move the task bar to the vertical left side of the screen, where I prefer it.

I really hate it when they eliminate features that people like.

https://www.neowin.net/news/windows-10-reaches-70-market-share-as-windows-11-keeps-declining/
thewayne: (Default)
This is a good move. They're migrating some core code libraries from C# to Rust. C# is not truly based on C and C++, it has characteristics of several languages. The language is pronounced SEE-SHARP and they wanted to use the musical sharp symbol, similar to the #, but it doesn't exist on pretty much every keyboard in the world, so they compromised and went with the name but the pound symbol.

The job is described as "...include "guiding technical direction, design and implementation of Rust component libraries, SDKs, and re-implementation of existing global scale C# based services to Rust."

The goodness is that Rust is a very tight language when it comes to memory strictness. Lots of languages are pretty loose when it comes to enforcing memory allocation and access, Rust is definitely not. This looseness is what gives hackers open doors to lots of systems. And this is why Linux is now rewriting a lot of its core systems in Rust from C and C++. Microsoft is doing the same thing with the Windows operating system. But this is a very slow process as there's far fewer Rust programmers than C/C++ programmers, so it's a slow slog.

If you know anyone who says they want to be a programmer, and they're serious about it, Rust and systems programming would be a very financially rewarding line to explore. Hard work, but well-paying.

https://www.theregister.com/2024/01/31/microsoft_seeks_rust_developers/
thewayne: (Default)
*sigh* At least it's been a long time since the last one, but it's going to be a rough transition.

Microsoft is taking away the Ctrl key on the right.

In its place will be a key for its CoPilot AI Assistant.

Won't that be just dandy?

The last change was when MS added the Windows key to the Natural Keyboard back in '94. But MS really wants people to use its AI assistant, so what better way than to make a key dedicated to it where people regularly use a normal key?

Here's the kicker: it's possible that it may not be able to be reassigned!

I was reading an article on Dell's new XPS series that's going through a complete refresh for 2024. They all have the new CoPilot key - to the left of the left arrow key - and it is immutable. Cannot be changed. That's definitely going to force a lot of people to retrain muscle memory who are semi-touch typists.

Personally, if they'd tied it to a function key, or left the key reprogrammable - that'd be fine. But if it is indeed not reprogrammable, that's going to be quite an issue!

https://arstechnica.com/gadgets/2024/01/ai-comes-for-your-pcs-keyboard-as-microsoft-adds-dedicated-copilot-key/
thewayne: (Default)
I'm glad it's coming from MS rather than HP!

From the article: "Earlier this month, Microsoft disclosed an odd printer bug that was affecting some users of Windows 10, Windows 11, and various Windows Server products. Affected PCs were seeing an HP printer installed, usually an HP LaserJet M101-M106, even when they weren’t actually using any kind of HP printer. This bug could overwrite the settings for whatever printer the user actually did have installed and also prompted the installation of an HP Smart printer app from the Microsoft Store.

Microsoft still hasn't shared the root cause of the problem, though it did make it clear that the problem wasn't HP's fault. Now, the company has released a fix for anyone whose PC was affected by the bug, though as of this writing, it requires users to download and run a dedicated troubleshooting tool available from Microsoft's support site.

HP printer app is installing on PCs whether they have HP printers or not
The December 2023 Microsoft Printer Metadata Troubleshooter Tool is available for all affected Windows versions, and it will remove all references to the phantom HP LaserJet model (as long as you don't have one installed, anyway). The tool will also remove the HP Smart app as long as you don't have an HP printer attached and the app was installed after November 25, presumably the date that the bug began affecting systems. These steps should fix the issue for anyone without an HP printer without breaking anything for people who do use HP printers."


There are many a day that I'm glad that I'm no longer in main-core IT. This is one of them.

https://arstechnica.com/gadgets/2023/12/microsoft-releases-downloadable-tool-to-fix-phantom-hp-printer-installations/
thewayne: (Default)
And all of your printers appearing to be HP lasers!

Doesn't that make you feel special?!

Theoretically your printer should continue working normally, unless you have third-party drivers. It's unknown if MS will be able to remove the driver and whether or not at that point what will happen to your printer configuration. Right now I'll bet IT staff are ready to go on a rampage at HP HQ! My home system is unaffected as I don't have printer drivers installed in it: I occasionally print to PDF files, that's it. If I need to actually print something, I mail the document to myself and print it from my laser attached to my Mac.

Microsoft claims it is a bug in the MS Store and has nothing to do with HP.

https://arstechnica.com/gadgets/2023/12/hp-printer-app-is-installing-on-pcs-whether-they-have-hp-printers-or-not/
thewayne: (Default)
What a long, strange road it's been. The intended cut-off date is 2027, but it may be moved further down the road past then, not a hard and fast date.

I hadn't heard about this, but there's a consortium of computer and printer makers called Mopria. From the article: "Mopria is part of the Windows' teams justification for removing support. Founded in 2013 by Canon, HP, Samsung and Xerox, the Mopria Alliance's mission is to provide universal standards for printing and scanning. Epson, Lexmark, Adobe and Microsoft have also joined the gang since then.

Since Windows 10 21H2, Microsoft has baked Mopria support into the flagship operating system, with support for devices connected via the network or USB, thanks to the Microsoft IPP Class driver. Microsoft said: "This removes the need for print device manufacturers to provide their own installers, drivers, utilities, and so on."
It should be noted that Samsung sold its printer division to HP, and I think most people know my opinions on HP printers.

Standardized printer drivers are a wonderful thing. Back in the early '80s when PCs first came out, you literally WROTE your own printer drivers. For standard printing needs like spreadsheets or program code or stuff like that where you didn't need formatting, you just shot the output out to the printer. But if you wanted to do word processing niceties like bold or underline or things like that, you pulled out the manual that came with the printer, fired up a printer driver program that came with the word processor, and entered a whole bunch of finicky codes that told your word processor how to talk to the printer to do things like bold, underline, etc. Proportional printing wasn't much of a thing in the early days until laser printers and desktop publishing came along a little later in the '80s.

I kid you not. It was a royal pain in the butt. Get a code wrong with a typo, or plug the wrong value into the wrong part, and you got results that were, shall we say, interesting.

So when printers largely became plug and play, you have no idea how nice it was compared to 40 years ago!

I remember around '86 or so I programmed a dot matrix printer, a tractor-feed Okidata, to print 1099 tax forms. I had it doing micro-line feeds and going back and forth to fill in the boxes on that form. It was fed from a database that I wrote in dBase III. It was a lot of work to get it to do it right, and some tricky coding, I kid you not. And I heavily documented the code, including a giant disclaimer that you could not miss that said "WARNING: DO NOT TOUCH THIS CODE AS IT INCLUDES MICROSPACING FOR PROPER FORM ALIGNMENT. You'll break the alignment!" After I left the company for a better job (they wanted to turn me back into a word processing typist), my boss's husband, who was a "professional", touched the code and broke it.

https://www.theregister.com/2023/09/11/go_native_or_go_home/

https://hardware.slashdot.org/story/23/09/11/1828213/microsoft-to-kill-off-third-party-printer-drivers-in-windows
thewayne: (Default)
I've never liked the Chrome browser, personally, for two reasons. It had an auto-update that at the time that I learned about it you couldn't disable, and it eats an awful lot of resources. And I don't use it except on a couple of PCs at work, not on my personal work station.

So let me give you a little background on how cookies can track you across web sites.

First off, don't go thinking that Google is mainly a search engine company. They are an advertising company. They make their money off of selling (functionally) ad space to companies through search results and looking at key words in your email. NEVER FORGET THIS. It used to be this was accomplished by what is known as third-party cookies. This was a special kind of cookie that could persist across web sites and browser sessions.

For example, you buy a pair of shoes off of Amazon. Amazon keeps a cookie (or three) in your browser's cookie cache that remembers some information about you, and theoretically no one except Amazon can read that information. So we have an Amazon.com cookie. Now, a super cookie is just a cookie with the name .Com and that's it. And because it's a top-level domain (TLD), apparently it can read some information below it, such as the Amazon.com cookie. It may not know what the information within the Amazon.com cookies means, but it knows the information is there and might be able to make some guesses.

Advertisers want as much information about people as they can get, supercookies are one such tool. Another tool is tracking pixels. These are invisible 1 pixel images that are inserted into a page or email that link to a server where the tracking pixel has a specific identity tied to the email or page that you open. If your email or web page doesn't block images or tracking pixels, when you open the page, that pixel is loaded - and the tracker database knows that specific pixel was loaded and ties that page or your email into tracking information about you.

Now, email programs can be configured to block tracking pixels and supercookies, which advertisers hate because they get less analytic information which means less information they can sell to potential ad or analytics buyers. And remember, Google is in the ad serving business.

Google came up with an alternative, baked into the browser that they want everyone to use. When you open Gmail, or Google Search, in Firefox or Microsoft Edge or Safari, you get this lovely popup: For the best experience, open this page in Google Chrome. Gee, wonder why! Now what Google is doing is they analyze the page that your browser is now looking at and generates a 'topic list', along with a unique identifier for your PC, and now they have analytics that they can sell for ad buyers! All without cookies! Oh, and it gets better! Google claims "a significant step on the path towards a fundamentally more private web."

BWAHAHAHAHAHAHAHAHA!

They also claim that they'll block third-party cookies in the second half of 2024. I think Firefox now does that by default. And while Microsoft Edge, which is a pretty good browser, is built on Chrome code, it can also block third-party cookies.

https://arstechnica.com/gadgets/2023/09/googles-widely-opposed-ad-platform-the-privacy-sandbox-launches-in-chrome/
thewayne: (Default)
First, a little explanation about Postscript.

Back in the early days of laser printers, in the '80s, Postscript appeared. It is actually a programming language for lasers that used math to describe vector fonts that allowed the explosion of desktop publishing to begin (as a programming geek, I have a book on it!). There are basically two types of fonts or graphics, vector and raster. A vector font is described using math or a formula, and as a result can be rendered at any size, from one point up to a size beyond imagination, and it will be the exact same design regardless. A raster is an image, and it may look fine at the resolution at which it was scanned or smaller, but when you start enlarging it, the quality of it falls off dramatically. You've all seen horribly pixelated examples of this, even if you didn't know what the technical details of it were.

One interesting thing about Postscript is the language would allow you to define a line that was one point wide and infinitely long! It would continue printing on that laser until the printer died, as long as you kept feeding it paper.

So, back to uneditable documents. And a little info on how PDFs work.

When you create a PDF, the font definition is embedded inside the PDF file. When you open that file on a computer other than the one that you created it on, your PDF reader program, which may or may not be Adobe Acrobat, says "This file contains Font X!" and looks to see if that font is loaded. If it is, then all is well and the font is loaded and the document continues processing for display. If Font X is not installed on the system, the PDF also contains information on Font X's "family", let's say that font is part of the Courier family, so the computer says to itself 'I don't have Font X, but I have lots of Courier fonts, so I'll grab one of those and continue rendering the document!'

The computer is happy and the document comes up on your screen, or gets spat out by your printer.

Now the problem. The earliest form of fonts in PDFs were Postscript, known as Type 1. And Microsoft, in their infinite wisdom, has pulled the Type 1 fonts from Office 365 as of the middle of this month. This includes both Mac and Windows. Open Office had already pulled support. If you bought Postscript from a third party, you should still be good.

According to Adobe, from the article, "[the] PDF and EPS files with Type 1 fonts will continue to render properly, as long as those fonts are "placed for display or printing as graphic elements." That text will not be editable, however."

Also, "If you want to see what kinds of fonts you have installed on your system, Windows and macOS will show you that information with a little tweaking. In macOS, open the Font Book app and switch to List view and font formats will be listed under the "Format" column on the right. In Windows 10 or 11, open the legacy Control Panel, select Fonts, switch to Details view using the button in the upper-right corner, right-click the top row, and check the "Font Type" box. PostScript fonts can also be identified by their file extension if you can see it, typically either .pfb or .pfm."

https://arstechnica.com/gadgets/2023/08/microsoft-adobe-and-others-have-dropped-support-for-old-postscript-fonts/

May 2025

S M T W T F S
    1 23
45678910
1112 131415 1617
18 19 20 212223 24
25262728 2930 31

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 5th, 2025 08:31 am
Powered by Dreamwidth Studios