MyWiki:Reference desk/Computing

From Wikipedia, the free encyclopedia
Latest comment: 18 December 2025 by ~2025-41612-53 in topic Two PDF options on print
Jump to navigation Jump to search

{{Wikipedia:Reference desk/header|WP:RD/C|WP:CHD}}


December 7

[edit source]

no sound on windows 10

[edit source]
Moved from Wikipedia:Village_pump_(technical)#no sound on windows 10
 – DVRTed (Talk) 05:39, 7 December 2025 (UTC)Reply

Have our Lords and Master at Microsoft decreed that we can no longer audio?

My windows 10 machine suddenly has no sound. When I try to turn up the volume, a window opens that says "We're here to help."

Does any rational person not suspect fraud? Are they trying to take me captive to sell me on an auction block to a plantation owner? Is it possible to run the Windows operating system without assenting to that? ~2025-37205-52 (talk) 05:24, 7 December 2025 (UTC)Reply

@~2025-37205-52 This is nothing to do with Microsoft. The sound on Wikipedia works fine for me. I suggest you check your connections and then try restarting your computer. Have you tried plugging in an external speaker? Failing that, take it to a repair shop. Shantavira|feed me 11:42, 7 December 2025 (UTC)Reply
Ask yourself, what changed? I normally don't bother with the Google seach assistant, but if you stick this query in the search box: Windows 10 no volume, a window opens that says "We're here to help." a number of apparently helpful suggestions appear. Rather than to-ing and fro-ing trying to work out just what your system/device is and exactly what the symptoms are, why not try those and come back with some more information? My favourite trick is to try Windows Restore to a time before the problem occurred. Best of luck, MinorProphet (talk) 10:05, 10 December 2025 (UTC)Reply

December 9

[edit source]

Microsoft Q&A problem (and a computing question)

[edit source]

I've been trying to ask the following question on the Microsoft Q&A site [1]:


I'm updating a WPF application that's written in C#. My development environment is Visual Studio 2023. The application currently uses .NET Framework 4.6.1, but I'm hoping to upgrade to a more modern version of .NET as part of the update.

The application uses a 32-bit COM dll, which I've called "DataTest" in the code below. This has been registered with regsvr32 and appears on the list of available COM objects in my project. When added to the "References" section, a DLL named "Interop.DataTest.dll" is created in my \obj directory, as expected.

The DLL exposes a single object, "CDataTest", with various properties and methods. I instantiate it as follows:

   using System;
   using DataTest;
   namespace MyNameSpace.DataTest
   {
       /// <summary>
       /// Wrapper for DataTest CDataTest object
       /// </summary>
       public class DataTest
       {
           private readonly CDataTest _dataTest;
           public DataTest()
           {
               _DataTest = new CDataTest();
           }
       }
   }

This works correctly when I build the application in "x86" or "All CPUs" mode. However, I now need to access a new 64-bit DLL, so I need to build the application in "x64" mode. When I do so, I get the following exception when instantiating CDataTest:

   System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {[GUID]} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

"GUID" is the GUID of the CDataTest object. Following the advice in another question on this site, I've added the following keys to my registry:

   HKLM\Software\Classes\CLSID\{GUID}
   HKLM\Software\Classes\AppID\{GUID}

The first key contains only a REG_SZ value "AppID" which is set to the GUID, the second key contains only an empty REG_SZ value "DllSurrogate". However, this hasn't fixed the issue. A 64-bit version of "DataTest" or a 32-bit version of the new DLL are not available.


However, when I try and post it, I get a message "This question has been deleted due to a violation of our Code of Conduct". I have two questions for Wikipedia:

  1. Does anyone have any idea why the question above violates Microsoft's Code of Conduct? I don't see any obvious Scunthorpe problem.
  2. Can anyone help with the underlying DLL issue?

Thanks. ~2025-37950-70 (talk) 18:13, 9 December 2025 (UTC)Reply

To answer the second part of my question:
  1. Create a new GUID using your favourite text editor (I used the one in Visual Studio). APP_GUID in the code below.
  2. In Regedit, find HKLM\Software\WOW6432Node\Classes\CLSID\{GUID}.
  3. Add a value "AppID" to this key, and set it to {APP_GUID}.
  4. Create the key HKLM\Software\WOW6432Node\Classes\AppID\{APP_GUID}.
  5. Set the (Default) value of this key to the DLL name (in my case, "DataTest.dll").
  6. Create a new REG_SZ value "DllSurrogate" for this key, leaving the value empty.
  7. Create the key HKLM\Software\WOW6432Node\Classes\AppID\DataTest.dll (or whatever your DLL name is).
  8. In this key, create the REG_SZ value "AppID", and set it to {APP_GUID}.

~2025-37950-70 (talk) 13:38, 10 December 2025 (UTC)Reply

December 14

[edit source]

Why is so much security camera footage shared by filming a screen?

[edit source]

Example here


Would it not make more sense for police departments to release the actual footage instead of just filming a computer screen with the footage playing instead? Is CCTV files really that hard to access Trade (talk) 05:39, 14 December 2025 (UTC)Reply

They may be closed proprietary systems without any easy means to export the file in a common format.
Additionally for security concerns, they may not even have I/O ports to reduce the risk of someone tampering with existing footage or introducing malware. cmɢʟee τaʟκ (please add {{ping|cmglee}} to your reply) 11:45, 14 December 2025 (UTC)Reply
A reason may be that this may be easier; the police department may not have the software or expertise to convert the format from what has been called a "maze of formats".[2]  ​‑‑Lambiam 16:41, 14 December 2025 (UTC)Reply

December 15

[edit source]

Two PDF options on print

[edit source]

I am using a Dell desktop computer running Windows 11. If I click that I want to print a page, I am commonly given the options of Save to PDF, Canon D570 (the printer that I have connected to the computer), Microsoft Print to PDF, and OneNote (Desktop). If I want a PDF, rather than paper, what is the difference between Save to PDF and Microsoft Print to PDF? Robert McClenon (talk) 20:20, 15 December 2025 (UTC)Reply

Applications like Word, Excel etc. have their own feature implementation to save the document as PDF. The Print to PDF is like a print driver that any application can use to print the document as PDF instead of a real printer. 05:54, 16 December 2025 (UTC) manya (talk) 05:54, 16 December 2025 (UTC)Reply
They are just two different virtual printer drivers that have a similar function but slightly different features. For example, on my computer, "Save to PDF" gives a choice of 10 paper sizes, while "Microsoft Print to PDF" gives 54 paper sizes. Any software can provide such a function and add it to the printer selection list. On my computer, I have Quicken installed, and there is consequently yet a third PDF selection in the menu, "Quicken PDF Printer" (which supports 149 paper sizes). There is probably little difference in the result if you choose "Save to PDF" or "Microsoft Print to PDF" unless you need a specific paper size not supported by the former. CodeTalker (talk) 21:27, 16 December 2025 (UTC)Reply
There is an extra difference. Save to PDF maintains metadata, like links. Print to PDF acts like a printer. You can't have embedded links printed on paper, so those are lost. I like to say that Print to PDF flattens the document. ~2025-41612-53 (talk) 15:47, 18 December 2025 (UTC)Reply

December 20

[edit source]