Tripredacus

My image dev machine runs Win 7 and can service Windows 10 images no problem, but I am only using MS provided tools.

Why this particular requirement? Is there something besides ADK components that require it?

Search has been fixed.

If you do have to use RDP then there are some mitigations. First you have to know that this would be something that would happen in an attack on a high value target. Because the attacker would need to know this information: - the IP or identifier of your computer - the username and password If the computer is not connected directly to the internet or in DMZ, it is less likely to be found. What you can do if you want to use RDP (may need XP Pro or use other methods to do this on Home) : - do not have Guest account enabled. If you are hosting network shares, you'll need to set an account for authentication. - create a new user group, this group should not have admin access but does have RDP access. - create a new user that is not admin, add it to that group. - set RDP to only allow logins from that user group. There are other ways to handle it.

May be relating to Year 2038 bug: https://en.wikipedia.org/wiki/Year_2038_problem

This CVE indicates that the attacker would connect into the computer using RDP and then run a program. How to handle this would depend if you are using RDP or not. If not, you can disable it and while the exploit would still exist, the ability to use it would not.

Politics (and religion) have always been forbidden topics on this forum. It was decided to leave the topic open, despite the fact that the pandemic has been politicised nearly everywhere. As long as the people who participate in this thread can post without bias and without involving politics or other things that are against the forum rules, then the thread can remain open. The freedom to speak against unjust things that are happening in our world (and on other websites/social media platforms) must be allowed in order to have a free people, they just cannot be discussed here.

Read today that UK uses a social distancing app that will inform people if they come in contact with a person or location where a positive result is reported, and inform them that they must isolate. The unintended consequence of how the app works seems to be that it is picking up phones (people) through walls, say in apartments or if you are driving the app may pick up a person on the sidewalk or in a building along the road. This article doesn't mention those examples (they come from people on twitter who say to just delete the app) but talks about how NHS isn't going to change the sensitivity of the software: https://news.sky.com/story/covid-19-no-plans-to-change-sensitivity-of-nhs-contact-tracing-app-after-half-a-million-people-pinged-in-a-week-12357177

Well it is good to know that clarification. What I specifically meant by my statement is that any discussion relating to the politics of the situation should not be discussed here. I do not know how it is in other countries but the entire topic is split by political ideologies in the US. I think that we should not forbid everything relating to Covid or the pandemic and that discussions relating to the technology programs (such as what you can run or put on your phone) is perfectly fine to be discussed here. Relative to this topic, I can share an anecdotal story in which a person on another forum I am on lives in Shanghai, and has had to use a similar thing there in Spring of 2020. Where he would have to show a QR code on his phone to the soldiers at the military checkpoints if he wanted to leave his neighborhood to go to a store or whatever.

When I look on VisualStudio.com I can only see LPs for that OS. It seems the old link to the Technet eval does not work anymore, it just redirects to a main site. I would look onto the secondary market to buy the System Builder version from which you can make an ISO.

I personally wish that those miniports did not get their own devices in newer OS, it makes ipconfig annoying to use.

This topic can remain open only as long as the software (or type of software) mentioned by OP is what is being discussed.

Vulkan was/is intended to be a replacement for OpenGL, is based off AMD's Mantle API and is supported on nVidia, AMD and Intel.

In the US there are plans to create that type of software, and some States have made it already but there is nothing from the top side of the government. So currently any such plans are at the discretion of the individual states. And as should be expected with any government software initiative, the programs themselves are wildly insecure and do not work for a lot of people. A complaint I often see for the app for my state is that people registered for it and then the app can't ID/find them or login or whatever which makes it useless for them. Currently, while these apps do exist, I am not aware of anywhere that actually requires them. Some places will accept them but no situations where you must have the app.

Perhaps it does explain why domain profiles often became corrupted on XP and 2000 systems often. Back then, people only learned of the term "Roaming Profiles" because their local profile would get corrupted and Windows would log in with the Roaming Profile that it pulled from the network. At one place I did some work at, they had a network "policy" (aka they told users to do it but you know how that goes) to never save anything into My Documents in order to keep the local profile size (and the synced version) down as they found that once profiles got larger than say... the amount of physical RAM on the system, the local profile would get corrupted. In their investigation of local profile corruption, they were seeing local user folders (or just My Documents) at 1-2 GB in size. There is also the situation where profiles were then syncing files that didn't need to be copied over, so them making these 3 folders to sort the different types of data does make sense.

The WAN Miniports were always there but are usually just not shown. There are some instances where a LAN installation on XP goes bad and is evidenced by the WAN Miniports appearing in Device Manager under Network Adapters. I noticed that I let out an audible groan this morning when I went to unlock my Win 10 PC, after seeing that it takes more than 2 seconds to unlock. This means that some update installed overnight and restarted the computer.

What launches CameraHelperShell.exe in the first place? Is it a service? Perhaps less annoying would be to set the service to manual, and only enable it when you want to use the webcam. Even a shortcut or batchfile with sc.exe could handle that on/off situation. Also as stated with the issue of blocking the writing to the file is 1) it doesn't stop the program from attempting the writes (it is still taking resources) and 2) doing so may generate an error being written elsewhere. I would also consider deleting and replacing that LWSDebugOut.txt on each reboot using a scheduled task. BUT I must say that it would be much preferable if you could find a program (or not use a program) that didn't write to the text file in the first place. For example, I do not know if the BisonCam software will work with that or accomplish what you need. Anyways, this reminds me of something I did on my old XP computer. An online friend had been infected with an AOL Instant Messenger virus and was having trouble with it. He asked how to stop it from doing what it was doing so he had sent it along to me. I had installed it on my own computer and it didn't seem to function because I was using Trillian instead of AIM. I still did use the paths and whatnot to create ACL rules to stop the virus from being able to do anything and sent the person those commands and it had solved the problem they were having. Since it didn't do anything on my computer, I kind of forgot about it until some months later when I ran out of hard drive space. Low and behold, there was a huge amount of text files that the virus had created which primarily consisted of "cannot find, cannot connect to" error messages.

Also imagine a program installer needing to be designed to not only support home users but users within a domain, is more likely to use %APPDATA% variable for compatibility. Since a standalone PC can still work fine with data in Roaming, while a domain-joined computer may experience a problem if a program only used %LOCALAPPDATA% variables and a user does actually use roaming profiles.

A recovery DVD from Toshiba or (as jaclaz says) the recovery image from the recovery partition can be used to reinstall the OS and it should show that it is activated. On the recovery DVD angle, it may be possible that any Toshiba recovery DVD (of the appropriate edition ie Pro, etc) can be used instead of the one specifically for the model, although there are some known instances where recovery media for an OEM cannot be mixed between models and/or countries. I know that when my company worked with Vista, we had to repress recovery DVDs for SP1, so there may be a service pack requirement for the recovery DVD as well. The key on the COA label is for show, but can be used to activate a System Builder installation using telephone activation. There is no garauntee that a PC from Vista era onwards came with a recovery DVD. Microsoft always has a requirement on the OEM to provide a recovery solution, be it on CD or DVD and even allowed (at that time) the ability for a customer to download an ISO but said ISO could not be publicly available. And if hard disk recovery was available, a physical DVD was not required to be supplied but was allowed to be sold or provided upon request. Vista was the first OS where Microsoft provided instruction on how to create hard disk based recovery, so it was at this point that OEM PCs stopped shipping with a recovery DVD in the retail space. Some OEMs had a software pre-installed that would let you burn your own recovery CD or DVD.

At first glance it seems that it either is not detecting the device properly, or the device detected is not something in the supported list. I'd first check to see if that HwID shown in the logs is actually present in your system or not. Look for the device in Device Manager and get the Hardware ID from the Details tab.

Microsoft never recovered from the bad reputation that Vista received at launch. It had bad press because it was slow an unreliable, but to understand that the average specs for a new Vista system were the same specs for an average Windows XP system at the time. So for example, a Vista computer with 512 MB - 1 GB RAM instead of say... 4 GB RAM that seems today to be a no-brainer. And it is true that Vista did have some other issues even with an appropriately spec'd system and all of Vista's issues were corrected by the time SP1 came out and Vista became viable. But the early failures never went away and people never knew it got corrected. So Windows 7 hype/marketing was more to get back a better opinion. You'll notice the same thing happened with Windows ME, and Windows 8 or 8.1, which also had rocky starts, and despite the fact that things got fixed and that they are fine OSes, they are still considered to be trash by the general public. An interesting outlier in this phenomenon is that of Windows 2000 which didn't work at all at launch for maybe up to a week due to bad driver support, yet somehow a cult following had developed around that OS early on and has never been seen as a failure like Windows ME.

I haven't got search to work since the forum was down last, and since then there was a forum software update.

Running on AC or battery? Silly thing to check to see if the power cord is actually plugged in and working.

The location of a file doesn't actually have anything to do with its architecture. But, normally if a program installs to Program Files (x86) it is the 32bit version not 64bit. It is the installer that determines where a program is installed, and the installer is just copying files. So you can have a 32bit installer put a 64bit program into Program Files (x86) or experience a similar thing with a modified or malfunctioning OS.

It appears that there is some updating of the forum software happening, which may explain why things aren't working as expected. As usual with IPB Forums, an update tends to break a lot of things.